Originally Posted by
John Coloccia
I'm waiting to see how it really shakes out. I think I'm running the "Pro" of 7 on everything anyway, but I'm waiting to hear from IT guys that they can effectively keep their systems running.
Restoring from a backup won't help if an update fails. It simply tries to reinstall it the next time you run Windows. There's no way simple way to stop it. If you're going to force people to take updates, they need to work across the board, every time...period. If they can't, and it looks like they can't, then it's a lousy idea that should be killed before it's had a chance to cause real damage.
Here is what seems like a decent overview of Windows 10 updates.
http://www.makeuseof.com/tag/turn-of...es-windows-10/
Microsoft’s New Updating Methods
Throughout the entire
Technical Preview a whole new scheme for updating Windows 10 was used. It involved fast and slow rings, which controlled how frequently updates were installed on the participant’s devices depending on which ring they belonged to. Now that Windows 10 is being sent out into the wild, update branches (described below) will be used to decide who gets updates at what time once they are available.
The most flexibility is with the Enterprise edition on the Long Term Servicing Branch (LTSB). This is only available for customers with a Volume Licensing Agreement (VLA) or Software Assurance (SA) and it allows any update to be postponed indefinitely.
In the middle, we have the Professional, Enterprise, and Education editions with the Current Branch for Business (CBB). It allows users to defer updates for an unspecified amount of time before they are forced onto the machines. This allows companies to test the security patches, fixes, and new features before rolling them out via
Windows Server Update Services (WSUS) or other compatible patch management systems such as System Center Configuration Manager, thus allowing more company control while still making sure all updates eventually get rolled out.
And at the bottom of our list we have Windows 10 Home which uses the Current Branch (CB). It allows
very little control over updates. The other issue that arises with the Home edition is that Microsoft has decided to apply the same behavior to all apps installed from the Store. A user can initiate an update check and install cycle, but you cannot select what updates will be applied. You simply get them all.
Microsoft has been pretty upfront about the fact that home users get Win 10 updates first and in waves. If there aren't too many screams of pain and anguish those updates are released to commercial users. At least that's how I understand it.