4 ms·
OTOH, the history of Windows 10 seems to be one botched update after another. True story, last week I tried to update Windows 10 v1803 (preinstalled) on my din
by em500 7y ago
OTOH, the history of Windows 10 seems to be one botched update after another.
True story, last week I tried to update Windows 10 v1803 (preinstalled) on my dinky ASUS VivoBook E12 to v1903. The result was a seemingly endless "Reverting changes" bootloop that I haven't gotten around to fix yet.
- 0xffff2 7y agoI had a similar issue one my Microsoft Surface a while ago. After several months of completely failing to install updates, it finally succeeded last month for reasons I can't figure out. The Surface didn't get much use anyway when this started, so I wasn't really interested in investing a lot of time if fixing it, but it's really amazing to me that Microsoft can't even get Windows 10 updates right one their own hardware.
- AnIdiotOnTheNet 7y agoYes, it is true, Microsoft has not taken good care of Windows in recent years.
- dejawu 7y agoYep, I had the exact same problem with v1903. In the end I had to make an install USB, reformat the disk and do a true reinstall (Windows claims it can do a clean reinstall of itself but it still keeps a ton of data and doesn't fix a broken installation)
- shpongled 7y agoI can't update to 1903 either. Continuously tells me that my PC can't run Windows 10 because they can't access the system reserved partition. It's going to take a manual reinstall, so I've been putting it off.
- skyyler 7y agoI don't think your experience is very common. Deploying Windows 10 to users from Windows 7 has been a lot less hassle than XP to 7 in my environments, and I haven't heard different stories from other admins.