16215 Fails To Install

[patseguin Global Moderator]

I've been an Insider for years and decided to switch back to the fast ring last night with the release of so many new features.

 

My computer reboots like normal and goes through the process to 26%.

 

After rebooting I get a quick flash saying "attempting to restore installation", then another reboot. After that reboot, I get a blue screen that says "inaccessible boot device". That is followed by one more reboot back into my original version of Windows. Anyone else have this problem?

 

EDIT: For anyone else with the issue, it is happening to others: https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/cant-update-to-windows-10-16215-inaccessible-boot/182f4e5d-98c1-4673-bce4-00ef23bb499d

[PGHammer]

That's odd - no fails here; not even on the newest notebook in the trail - an ASUS X54C.  It has the most powerful CPU of all my Insider hardware - understandable, as it has the only Core-i anything in said arsenal (Core i3-2325 - SandyBridge).  However, it also has the second-worst GPU in the arsenal (one of only two non-DX11 GPUs among the notebooks) - only Big Pavilion - at DX9c - is worse; amusingly, it is Big Pavilion that it will replace when the Fall Creator's Update cycle ends.  The Intel HD3000 iGPU in the X54C supports DX10.1 features - not DX11.  For that reason, the X54C is more a productivity book than any other sort of notebook.

 

What CPU and GPU are in the hardware in question?  Also, how much RAM?  Is the HDD nearing capacity?  The X54C - like both HP Pavilions - has a 500GB SATA platter drive, 4GB of RAM, and a SATA DVD burner; also, like Baby Pavilion, it originally shipped with Windows 7.  (Big Pavilion came with Vista on board - hence the DX9c halt.)  Unlike Baby Pavilion, the X54C takes only a single DDR3L SODIMM (Baby Pavilion can swallow two); therefore, the ONLY upgrade in the X54C's cards is an SSD.  With so many notebooks hitting the wall, I'm having to look hard at replacing each notebook as it becomes un-updatable - and those certified/reconditioned Surfaces are looking real good as swap-ins - IF Pentagon City - the nearest Microsoft Store - keeps them in stock, as they tend to sell out rather quickly).  And I just checked - not so much as ONE in stock - at ANY Store within 120 miles; that is four states worth of Stores - VA, MD., DE, or PA.

[mfarmilo]

I'm seeing this on both of my Insider PCs - one is an Intel machine, the other AMD. I haven't yet confirmed it's the same error on the Intel one, but the AMD one just goes to a GSOD (what used to be a BSOD) with INACCESSIBLE BOOT DEVICE shortly after the 30% reboot, before the percentage screen reappears. It does this twice, then restores the previous version (16199). The AMD machine has a 120GB SSD for the system drive with 36GB free on the C: drive (which is the only partition on that drive apart from recovery partitions etc), and it has 8GB of RAM. Neither machine is set up in UEFI mode - the Intel one is too old anyway, and the AMD one is set in Legacy mode. I've done the usual CHKDSK on the system drive, and SFC /SCANNOW, as well as deleting the $WINDOWS.~BT folder but after 5 or 6 tries it still does it. Something odd going on, as others are experiencing this.

 

[+Tantawi Subscriber²]

I had the problem for two days it drove me crazy, tried every trick in the book, nothing fixed it EXCEPT uninstalling Samsung Magician + Acronis True Backup, rebooting, then trying the install again and it worked! reinstalled the same software later and running fine so far.

 

Others have fixed it by uninstalling third party Antivirus software like NOD32.

Edited June 10, 2017 by Tantawi

[PGHammer]

1 hour ago, Tantawi said:

I had the problem for two days it drove me crazy, tried every trick in the book, nothing fixed it EXCEPT uninstalling Samsung Magician + Acronis True Backup, rebooting, then trying the install again and it worked! reinstalled the same software later and running fine so far.

 

Others have fixed it by uninstalling third party Antivirus software like NOD32.

I don't have any third-party AV on any of my Insider hardware - in fact, I've stayed away from third-party AV since Windows 8.x (for the rather sane reason that Windows Defender has proved itself).  Given a choice between first-party software and third-party software, the ONLY reason to go third-party is if the first-party software fails - no ifs, ands, or buts.  Both Windows Defender AND DIsk Optimizer have proven themselves - unexpected in both cases; however, I can't fault either.

[baloor]

Can confirm. Uninstalling Samsung Magician application resulted in successful update to 16215

[mfarmilo]

Just to update - I still have this problem on both machines. Neither of them has the Samsung software mentioned above. Indeed, one of them has no third-party software at all on it. I have however noticed noone seems to have mentioned they're using UEFI boot mode, and wondered if Legacy mode might be a common factor in this problem?

 

 

[Sulphy]

I had a similar issue with various builds of Win10... i found however, that i had to unplug my bluetooth usb reciever for my Logitech mouse, then the install/upgrade goes through just fine.

[+Tantawi Subscriber²]

8 minutes ago, mfarmilo said:

Just to update - I still have this problem on both machines. Neither of them has the Samsung software mentioned above. Indeed, one of them has no third-party software at all on it. I have however noticed noone seems to have mentioned they're using UEFI boot mode, and wondered if Legacy mode might be a common factor in this problem?

 

 

I always used UEFI secure boot. Others have mentioned switching to legacy mode with no effect on the problem either. 

[Samson291]

I had a similar issue getting stuck at 30% disabling rapid mode in Samsung Magician on my D drive fixed it for me right away.

[cosrocket]

I'm having the same problem on my HP laptop. Doesn't have a Samsung SSD so no Magician software. I've tried to install build 16215 at least 5 times, and every time when the update hits 26% it reboots and says restoring previous version of Windows. Was hoping it was my Logitech wireless mouse transmitter but I just tried again without it and still having the same problem.