The IT Nerd

The fine folks at Microsoft put out a blog post which trumpeted it’s use of AI to deliver a smooth roll out of the Windows 10 April 2018 update. Near the end of it, they say this:

Based on the update quality and reliability we are seeing through our AI approach, we are now expanding the release broadly to make the April 2018 Update (version 1803) fully available for all compatible devices running Windows 10 worldwide. Full availability is the final phase of our rollout process. You don’t have to do anything to get the update; it will rollout automatically to you through Windows Update.

Quality and reliability? Seriously? Tell that to the people who have been hit by issues related to this update. Most notably this one where your computer is basically unbootable after the update. Now I do have a fix for it but this issue should never have made it out of Microsoft’s QA labs. Then there’s this issue which to Microsoft’s credit they have fixed. And let’s not forget this issue which has been fixed as well. I could go on but I think you see my point here. Which is that this issue has been insanely problematic and Windows 10 users have suffered as a result. And that should never ever happen.

So Microsoft may say this update is ready for prime time. But I say that you should take that with a grain of salt. But if you fell like rolling the dice on this, make sure you have a backup of your computer in case things go south. Which is entirely possible given what has gone on to date.

If you’re a Windows 10 user, and if you installed all the updates that showed up on yesterday’s Patch Tuesday dump, you’ve just fixed a really serious security issue with your Windows 10 computer. Specifically there was a vulnerability where Window 10’s ever helpful virtual assistant Cortana could help an attack bypass the computer’s lock screen and change the password. Now if you guessed that Cortana was always listening for commands to act on even if the computer is locked, you’d be right.

Now I know that when I try to use certain commands with Siri when my iPhone is locked, Siri will demand that I unlock my iPhone. Plus I can disable “Hey Siri” commands  at the lock screen entirely as that has been an issue in the past. Thus maybe Microsoft should look at doing the same. Otherwise, they’ll continue to have a never ending stream of lock screen security issues like Apple has had.

Which? conducted a survey of more than 1,100 people which looked at issues that users have had with Windows 10. And the results are not good if you’re Microsoft. Specifically:

• 21% of complaints had to do with issues with software compatibility
• 16% of complaints had to do with hardware/peripheral problems
• 7% of complaints had to do with email not syncing
• 6% had to do with the removal of non-Microsoft software
• 5% had to do with the PC slowing down
• 10% was classified as “other”

Now the PC world has a ton of hardware and software in it. Which means you can easily get a mix that causes havoc that users cannot solve themselves. Thus 46% of those who responded had to pay someone to fix those issue for them. Largely because Microsoft’s own tech support isn’t up to standard according to Which?

Clearly Microsoft has an issue as we’re three years into Windows 10 which the company calls the “last version of Windows” that they will be kicking out into the world and people are not happy. Which? says that Microsoft really needs to step up their game here and I agree. I stay employed because of the items mentioned above. And frankly, I shouldn’t be. Microsoft should have an OS where having to reach out to someone like me is the exception and not the rule. But that’s clearly not the case and I don’t seriously expect that to change from Microsoft which is a shame.

Since the release of the Windows 10 April 2018 update, users have faced a pretty serious bug where you get this error message about the desktop being unavailable:

This error message pops up right after installing the Windows 10 April 2018 update. As I type this, there doesn’t seem to be a fix from Microsoft. But six of my clients have been hit by this, and it’s been documented by yours truly as well as places like Microsoft’s own discussion boards, and Reddit. So it’s a pretty widespread issue. In each of the cases that I’ve had to deal with this, this is how I have fixed it:

1. On a different PC, go to https://www.microsoft.com/en-us/software-download/windows10
2. Download the «installation media tool».
3. Put it on a USB flash drive (8gb or more).

Now you need to go over to the affected Windows 10 computer. Boot it and you’ll get the error that you described. Don’t click «ok». Just leave it, press ctrl alt delete and open task manager. Then do the following:

1. Insert the flash drive in the affected computer.
2. In task manager, click «file» -> «run» -> «browse». Locate the USB flash drive and run «setup».
3. Let it run. It may take 90 minutes.

The net result is that you should have a working computer with all your data and apps installed.

As for what my clients think of this issue, here’s what one of my clients said:

As you can imagine, it’s infuriating because this is entirely because of Microsoft, not some 3rd party program or virus that messed up my computer. There should be a class action lawsuit against Microsoft, not that it would ever get anywhere.

While there has been some assertions that this is caused by AVG and Avast antivirus, I’ve had clients who haven’t had either antivirus application. Thus Microsoft has a serious problem and they really need to step up and fix this. Because this is clearly affecting lots of people, and that should not happen. Ever.

If you’ve never heard of GitHub, that’s okay. Here’s what you need to know about it. GitHub is the code repository company popular with many software developers. It is an essential tool for coders. Many corporations, including Microsoft and Alphabet Inc.’s Google, use GitHub to store their corporate code and to collaborate. It’s also a social network of sorts for developers.

The only problem is that they have lost money. Thus Microsoft appears to have swooped in buy the company. The deal could be announced as early as today. But even the mere rumblings of Microsoft buying GitHub has caused a swift backlash because many feel that Microsoft simply can’t be trusted given their past history of embrace, extend, extinguish when it comes to anything that Microsoft sees as a threat. For example a petition that seeks to “stop Microsoft from buying Github” had garnered support from more than 400 developers. And rival code repository SourceForge has a tool that will import your GitHub project to SourceForge. So this purchase may go ahead, but you can expect a lot of blowback.

Watch this space for updates.

UPDATE: That didn’t take long. It’s now official:

UPDATE #2: The exodus from GitHub has begun as TNW reports many developers jumped ship even before this was officially confirmed. And the company itself has confirmed the exodus:

Windows 10 April 2018 Update has been a mess with multiple issues affecting users. One of which was an issue with users of Intel’s SSDs which was bad enough that Microsoft stopped allowing PCs with those SSDs to upgrade to the April 2018 Update.

Well apparently that’s been fixed. KB4100403, was released by Microsoft yesterday and in the notes is the mention of a fix concerning power regression on systems with NVMe devices from “certain vendors”. Which later on this release notes specifically mentions Intel and Toshiba.

But there’s a catch.

Users of the Intel SSDs are encouraged to wait until May 25th if they haven’t upgraded to the April 2018 Update to do said update. Users of Toshiba SSDs are encouraged to wait until June. And in both cases, only upgrade when the upgrade is offered to you. Just make sure you have a backup and all that good stuff first.

The Windows 10 April 2018 Update seems to be riddled with issues. The latest issue has users reporting that the entire desktop is disappearing randomly.  And then they get this warning:

C:\WINDOWS\system32\config\systemprofile\Desktop is unavailable

That’s helpful. Not.

There’s a bunch of random fixes that are being mentioned online. Including some mentions of Avast anti-virus being the cause (and removing it being the fix). But at this point given how unstable this update is, the best thing to do is to roll back to the Fall Creators Update. If you haven’t updated yet. Don’t.

Maybe Microsoft should have left this update until May, as opposed to pushing it out on the last day of April?