Newsletter Archives

  • Pulling the trigger on Win10 Version 2004

    Logo

    UPGRADING WINDOWS

    By Susan Bradley

    Windows 20H2 is in the pipeline — so it’s about time to install … its predecessor, Win10 2004.

    On October 20, Microsoft tweeted that the October 2020 Update (aka 20H2) has been officially released and will show up over time via a “throttled” rollout. But a few of the tweet’s replies quickly noted that some Win10 users are still waiting for Version 2004 — or had to manually install it. (Microsoft states that the upgrade from Win10 2004 to 20H2 should go faster because it’s more like a monthly update.)

    Read the full story in AskWoody Plus Newsletter 17.42.0 (2020-10-26).

  • When Windows 10 Feature Updates don’t go smoothly

    Last weekend, I decided to bite the bullet and update a Win10-1803 Pro machine to Win10-1809, using Windows Update. I’d taken a system image backup, and as it wasn’t my production machine, I wasn’t too worried.

    This machine is under a year old, a purchase necessary when a hardware failure put paid to my trusty Win7 Pro laptop. It allows me to work more than I can manage at my desktop, and does most of the hard yards online, especially here.

    Windows Update installed 1809 x64 2019-10B – this was before Woody changed MS-Defcon from 4 to 2. It took 20 minutes to Prepare to Install, and nearly 2 hours to download, and several hours to install.

    Needless to say, it didn’t go to plan… The first indication of a problem was after several hours of installing, when a blue screen appeared bearing the words “Stopcode” and “Bad Pool Header”. It restarted, still on 1803, pending install. It continued installing. Eventually it restarted, and I was able to see KB 4521862 and KB 4519338 had installed – along with a bunch of drivers being updated, when the Pro settings were not to download drivers from Windows. I also noticed I hadn’t had to reset the Metered Connection settings to allow the update to download!

    After it finished its update, it wasn’t working properly. It looked fairly normal, but restarting started problems – none of the visible desktop items actually worked – not the Start button, any of the TaskBar icons, or anything other than the Ctrl>Alt>Del routine.

    I tried Sign Out. It took ages. It caused a loop of: Hi; We’re getting everything ready for you; This might take several minutes – don’t turn off your PC (that part remained until it got to Hi again); Leave everything to us; Windows stays up to date to help protect you in an online world; Making sure your apps are good to go; It’s taking a bit longer than expected, but we’ll get there as fast as we can. This loop took 5 minutes to restart, again, and again, and again.

    It had been over 12 hours since the process started at this point. As I had to do my day job, I just left it chugging away in the background while I got on with earning an income. Over 5 hours later, it finally came up for air – a desktop, but still not functioning.

    Along the way, I saw various errors:
    Error 0x80072EE7
    The gpsvc service failed the sign-in – access is denied
    windows\system32\config\systemprofile\desktop is unavailable

    To add to my woes, it wanted to restart itself again, where it re-entered the 5+ hour loop. I still had work to get done, so I just let it be. No stopcodes this time, but still it didn’t work.

    I couldn’t access safe mode, even with Recovery Tool USB access. Start Up Repair “couldn’t fix [the] PC”. Using the Recovery Tool, I was able to access the Command Prompt, where SFC /SCANNOW reported “Not enough memory resources are available to process this command” the first time, and then, after it went through 100%, “Windows Resource Protection could not perform the requested operation”. Attempting to use Restore Points was another failure – they were listed, but “unavailable”.

    At this time, I decided it was time to try to restore the system image. Again, the gpsvc error. Apparently there had been some issue prior to the update attempt? I had to put it aside for a few days, until I got time to address it properly. By this stage, I was heading for an ISO file on a USB stick. This laptop now needs to be reset from the ground up, going back over all the metered connection, deferred updates, Customer Experience, Start Menu apps settings etc. etc. etc. – and I’m sure there’ll be something important I forget!

    Having got the ISO installed, I was able to run SFC / SCANNOW and DISM /Online /Cleanup-Image /RestoreHealth. All 100% clear, thank goodness.

    There are only 5-6 programs to reinstall. If this had been a production machine, I’d have dozens of programs to have to reinstall. It’s still going to take another day or two until I get it back to normal, as I have other things I need to prioritize. If I’m a bit cranky this weekend, you now know why!

    I’m really lucky I have a wealth of knowledge, support and expertise here at my disposal. A normal home user would have ended up paying for professional technical support, and if it had been my production machine, would have resulted in a loss of chargeable hours. I’m counting my blessings!

  • Hedge your bets: Download an official, clean copy of Win10 version 1903 (build 18362.356) and save it for a rainy day

    You can get a copy of Win10 1903 whether you’re running Windows or not. Might prove nice to have on a rainy day.

    Full step-by-step instructions in Computerworld. Woody on Windows

  • Thurrott: Microsoft posts downloadable disc images of Windows 7 and 8.1

    You need a valid 25-character product key to be able to download the ISO for Win7 or 8.1.

    Paul Thurrott on Thurrott.com.

    Another really dumb decision reversed.

  • Microsoft has posted official ISOs of Build 15063 – sure to be Win10 Creators Update, version 1703

    Although the web site says you have to be a registered Windows Insider, in fact that doesn’t appear to be a requirement.

    As you’ve read, I strongly recommend that you not install this version until the bugs get shaken out – likely in July or August.