So did you end up with Windows 10, version 1703 installed on your machine last week? Or did you have a computer where it attempted and failed? Were you as surprised as I was by the installation?
Am I admitting that I, Susan Bradley, the Patch Watch lady, was totally caught off guard that last week 1703 was declared Current Branch for Business (CBB) and thus would be widely released to everyone who chose to defer the feature release? Am I admitting that I, Susan Bradley, the Patch Watch lady, was, or rather, still is confused about the new updating cadence, new name for the feature releases and new patching options? Yes and yes. I’m still trying to figure out the new normal for patching Windows 10.
Let me tell you what I am sure of: Microsoft loves to keep changing the rules, we need to roll with the flow and hopefully this will be the last major change in updating naming and timing.
The names and timing we used to have was called Current Branch (what Home version computers are on) or Current Branch for Business (what Pro versions can opt to do). Last week if you had Windows 10 1607 and had opted to defer feature updates in the user interface or in the registry or in group policy, you were offered up 1703 release. For those that had issues installing 1703 or wish to push off the update even a little longer, you can use the Show hide tool to temporarily block 1703 from installing on your computer.
If you’ve had issues installing 1703 and it’s rolled back, I’d start by looking for a new video driver from your video card manufacturer as the Creator’s release is very finicky about the video drivers installed. I’ve seen many a failed feature install get fixed by finding and installing a video driver. I would strongly recommend going only to the vendor of your computer or the vendor of your video card as I’ve seen malware on sites that advertise drivers. So be careful when searching for drivers and when in doubt, post in the Windows Secrets lounge and I’ll see if I can help out.
