A chimpanzee and two trainees could run her!
Oh for the love of Pete…
Yes, I ran into even more Windows 10 activation issues recently.
I didn’t even do anything wrong.
This time, it was a spontaneous message that my Win 10 Pro on my main desktop puter was not activated – just, well, because…
It turns out this was a known bug that MS has supposedly fixed.
Yes, I’m afraid I’ve had it…
Another Windows 10 upgrade is here: the Windows 10 October 2018 update.
For those of us using WSL, or “Linux on Windows”, that means potential mayhem.
When the last Win 10 upgrade version was released, I installed it. I then discovered that my Ubuntu icon no longer loaded anything – except a Bash window with an error message that Ubuntu on Windows was no longer installed!
Oops.
Fortunately, it’s pretty easy to fix!
A little over a month ago, I had the opportunity to upgrade a whole slew of Win 10 machines.
Back then, I wrote this article: Reactivating Windows 10 after a second major hardware upgrade
Now, I thought I had everything figured out in terms of re-activing Win 10 after a hardware upgrade.
However, it seems things have changed in even more ways than I thought.
SIGH (again)…
If you’re running Ubuntu or another linux shell in Windows 10 via WSL (Windows Subsystem for Linux), you’ve probably wondered about using cron.
Cron is super-handy for doing things, like, running a backup.
You see, as useful as WSL is, it stores all the linuxy files in a way that is not exactly easily backup-able by File History or anything else… as far as I can tell.
Worse yet, even when you try to set up a cron job to run a backup, it doesn’t work!
What to do, what to do?
So this is a fun one!
You have a file on your desktop. It can be anything: PDF, Word Doc, text file, whatever.
You try to delete it.
Instead of going into the Recycle Bin, you just get the “deleting” dialog box with the progress bar, and then…
Nothing happens! YAY!
I recently ran into a little problem: I upgraded a puter that had Windows 10 on it, and Win 10 refused to reactivate afterwards!
Now, you might have read my guide here: Upgrade your motherboard without reinstalling Windows 10
Well, it works.
But… It appears there is a limit to the number of times you can upgrade the hardware in your puter before M$ will insist on a call to their beloved Tech Support line.
SIGH…
The Windows 10 “April 2018 Update” version 1803 was released a few weeks ago… in May, not April.
Go figure.
Initially, there were some serious problems with 1803, but those seem to have been ironed out now.
Chances are, if you don’t have it already, you’ll be getting it soon.
Given my past articles on improving the privacy and security of Windows 10, what do you need to know about this new 1803 version of Windows 10?
In the olden days, there was only “Bash on Ubuntu on Windows 10”. This little gem gave you something like reverse WINE.
You got an Ubuntu linux install that’s running on top of the Windows kernel – with full file system access, the ability to install and run all kinds of linux command-prompty stuff like git, and even graphical linux apps like gitk.
Fast forward a few years, and things have changed…
What if you’re still running Bash on Ubuntu on Windows (Ubuntu 14.04) and you want to upgrade to the latest Ubuntu 16.04 without reinstalling everything?
Or, what if you want a different flavor of linux?
Back in October 2017, Microsoft released the Fall Creators Update for Windows 10.
For most people, all was well. But for a surprisingly large minority, the Start menu just sort of stopped working.
Clicking the Start button did nothing, and neither did right-clicking it. Sometimes, open apps won’t even show up on the taskbar.
Apparently, it’s still not working right for some people 5 months later!
There have been a variety of fixes for this issue, but there is one that I have found always fixes the problem…
Way back in 2009, I wrote this article:
How to Determine the Master Browser in a Windows Workgroup
I also released a tool called LAN Scanner that lets you see all the puters on your local network, their IP addies, MAC addresses, and which puter is the Master Browser.
That’s great… except that recently, it stopped working!
While digging into this problem, I discovered that the traditional “Network” browsing in Windows has kind of become broken since Microsoft has officially poo-pooed (and disabled) SMB v1.
What that means for you is that if you have a home network with Windows 10 machines, you’re going to want to switch to using a HomeGroup – but there’s a catch!