It's had it's up's and down's and just before Build 9926 was released I was hovering over the F12 key to rebuild it back to Windows 8.1.
However I persisted and happily updated to the latest build (9926) and so far, touch wood, it's been much more stable for me, before I was rebooting 4-5 times a day due to crashes and so far I've not rebooted since finishing the installation & patches etc.
However, on that note of patches, I did hit a snag.
See I've still left my device to be managed via System Center 2012 R2 Configuration Manager (yes, I know it's not "supported") and this also means I let ConfigMgr handle the Windows Update side.
This has a slight problem, since ConfigMgr/WSUS isn't aware of this strange OS called Windows 10...
I could go and change my policy in ConfigMgr and exclude my device from receiving managed updates, but that means creating collections, and device settings etc etc.
Normally with previous builds I've just been heading to the Control Panel, Opening Windows Updates and clicking the link to bypass administrator managed updates and check directly online.
But with Build 9926, imaging my horror when I couldn't find Windows Update in the control panel, only it's new modern equivalent, which doesn't allow you to bypass and go direct.
Thankfully, a minor registry edit will bring it back.
Simply add the following value (IsConvergedUpdateStackEnabled & UxOption) to the key paths shown below, or if they already exist change the value to 0 to enable WSUS back in the control panel.
And close and reopen the control panel for Windows Update to reappear!
Cool, now I can bypass ConfigMgr/WSUS and go direct again to check for Updates.
Alternately, GPO doesn't allow direct check for us so I simply run below in a .reg file every morning and then simply go to PC Settings > Update and Recovery and do a check:
Windows Registry Editor Version 5.00
I possibly don't need to remove all of above, the last one alone might be sufficient ...
Yep, had to do that in the past too :)
Post a Comment