Windows 10 Anniversary Update reverts to v1511 by itself for some

Ivan Jenic
by Ivan Jenic
Troubleshooting Expert
6 Comments
Download PDF

Problems caused by Windows 10’s latest major update, the Anniversary Update are just piling up lately. The latest reported issue we found on Microsoft’s forums is a problem with Windows 10 reverting itself from version 1607 back to version 1511.

This is a very strange issue, and surely a very annoying one, because people literally waste time and efforts for nothing. According to some Windows 10 users, who complained on the Community forums, Windows 10 normally received and installed the Anniversary Update, but after the first restart, it just got back to the previous version.

Ad

Microsoft actually never confirmed this issue, so it probably won’t even release a patch for it. But what’s even worse is that there’s currently no solution that will work for everybody facing this problem. A few Windows 10 users tried to solve it by performing actions like disabling antivirus, or restarting Windows Update, but unfortunately, the issue was still present.

“Hi, I’m updating the anniversary update with my ASUS ROG laptop. The update was successful and things went well at the beginning but until I restarted or shut down and turned on my laptop again it just automatically restarted after the ASUS startup screen at the blink of an eye and says “restoring previous version of Windows”. This is so frustrating and I can’t choose not to update those updates (limited internet). I googled about my problems, none of it worked. My laptop is new and I wish someone can please help me with this problem. Thanks.”

What we can advise you to try is to clean install the Anniversary Update, instead of downloading it via Windows Update. Microsoft already released ISO files and the Media Creation Tool, so you can easily create a bootable media with the Anniversary Update, and install it on your computer. However, we can’t guarantee that performing a clean install would surely prevent your system from reverting, but if nothing else could be done, it’s worth a try.

In case you encountered this, or similar problem, and you managed to find a solution on your own, please share it with us in the comments, because we’re sure it would be helpful to other users.

RELATED STORIES YOU NEED TO CHECK OUT:

Ad
    • ESET is not the issue. It’s either the M.2 NVM SSD or a combination of that with using SATA3 SSDs – OR it is an ASUS issue. Still trying to work this out.

      • Hi Benita, I too have a M.2 NVM SSD (Samsung SSD 950 Pro Series NVMe 256GB) as well as an ASUS board (ASUS Z97I-PLUS) were you able to pinpoint this problem? It happens to me as well.

        • Hi – no exact cause. Make sure you read my last post – it is long and it explains how I was able to make this all work. If you ask me, the problem is with the way Windows 10 handles multiple drives. I did nothing special except do a barebones install without the drives, and I unplugged all the USB connections except for the essentials. Let me know if you have any other questions.

          • incredible. it did work for me. I unplugged all drives except the nvme, where windows is on… then ran the Media creation tool to trigger the update… it sucessfully completed, and after rebooting.. it didn’t revert. now I was able to reconnect all drives and it stays updated. 🙂 thanks