Solved BSOD SETUP_FAILURE during repair install

have you considered attempting the upgrade in safe mode
that should bypass most upgrade problems and should give you a better idea if its the SSD.

best of luck, Steve ..

XxXxX said:

have you considered attempting the upgrade in safe mode
that should bypass most upgrade problems and should give you a better idea if its the SSD.

best of luck, Steve ..

Click to expand...

Not tried, the upgrade itself works (all the files copy to the drive without errors) but always fails on the first restart.

The drive is already used as the system drive and doesn't cause problems. I think there's some compatibility problem with Windows and the 9100 when doing an install

as you have a clone backup of the system now on the SSD would it not be an idea
to wipe the drive and do a clean install.

best of luck, Steve ..

XxXxX said:

as you have a clone backup of the system now on the SSD would it not be an idea
to wipe the drive and do a clean install.

best of luck, Steve ..

Click to expand...

Takes too long to reconfigure and I can't guarantee a clean install would work with the drive either

BrianInEngland said:

Takes too long to reconfigure and I can't guarantee a clean install would work with the drive either

Click to expand...

if you do a clean install you can bring back the clone to over write the new install
then do an upgrade of the system with all your software and settings in place.
this should be able to upgrade as the install of that version of Windows has already been installed.

i also assume that the current system is EFI/boot and GPT.
a bit long winded but there seems to be getting fewer and fewer options.
best of luck, Steve ..

XxXxX said:

if you do a clean install you can bring back the clone to over write the new install
then do an upgrade of the system with all your software and settings in place.
this should be able to upgrade as the install of that version of Windows has already been installed.

i also assume that the current system is EFI/boot and GPT.
a bit long winded but there seems to be getting fewer and fewer options.
best of luck, Steve ..

Click to expand...

That won't work - doing a clean install then restoring the clone would over-write it again, back to where I am now where I can't do an in-place upgrade on my existing install using this drive.

When I get chance I'll do some experimenting. I'll try a few things.
At the end of the day the Windows image gets written correctly (I've watched it go to 100% and restart) so it's got to be there somewhere!

Most likely some sort of Windows bug rather than hardware but who knows

Another update on this. It's highly unlikely to be a hardware problem as Windows is already running on this 9100 SSD and everything is stable.
Must be something going on with the ISO or a bug somewhere
The crash happens before it even gets to the 'Working on updates' screen - and the BSOD is actually a GSOD as I'm on Insider release preview - strange that I'm getting a green crash screen before Windows even loads!

OK I tried again today, same problem but I did do a few other things....

Run Setup.exe from Windows ISO as normal
Files copied 100%, no problems
First reboot - Windows logo and spinning circle for a couple of minutes, then SETUP_FAILURE crash (GSOD Insider RP)
Power off and reboot - Windows logo with no circle, no boot

At this stage I restored only the EFI system partition from my Macrium image (a known good working one as it's the one I'm using now)
Reboot - Windows logo and spinning circle but this time, it started the next stage of install after about 30 seconds (slightly bigger text on screen)
A couple of minutes later, black screen but no crash error, then my Desktop appeared with the error shown in the pic.

Restored my existing System partition, all is fine now. Boots into Windows every time and the system is stable

There's either something not right with the ISO, or the BIOS or Samsung 9100 drive isn't liking something - if that was the case I'd likely be seeing other errors?
When I last did it in Feb I was using the 26100.1742 ISO, with a 990 drive and a different BIOS version so these are the only things that are different this time

I also made a Macrium image of the failed install before restoring so I can look at some of the logs


Just to add, DISM scans and SFC all showing no errors, I ran these after the Windows update yesterday.

Once I was having the same error code. That was a driver error and it happened to be, in my case, Realtek driver error. I disabled Realtek driver in Startup folder in TaskManager and Windows installed properly. After Windows installed, I enabled the Realtek startup executable and no problems afterwards.

This happened a long time ago, though. I am sharing this just for your info.

suatcini54 said:

Once I was having the same error code. That was a driver error and it happened to be, in my case, Realtek driver error. I disabled Realtek driver in Startup folder in TaskManager and Windows installed properly. After Windows installed, I enabled the Realtek startup executable and no problems afterwards.

This happened a long time ago, though. I am sharing this just for your info.

View attachment 138818

Click to expand...

My RealTek audio is disabled in BIOS and no software for it is installed
Good suggestion though!

Anyone with some knowledge on these things feel free to peruse the logs from the failed install
I can't see the setupact.log file as it's over 400MB and it won't open for me


(Dropbox link)

Another note: There's no windows.old folder in the failed install but the free space is ~32GB smaller than the working install

OK I tried to do the install using the 26100.1742 ISO from October
This time it got past the First boot phase and restarted without crashing but then I got this (after reversing changes message)

Please run and post share links:



1) Upgrade failure info:





2) Tuneup plus:




3) the V2 log collector:

I'm not getting BSOD with the older ISO 26100.1742, the install fails at the second reboot stage now.

The log collector required a name.

The collector can be used for multiple purposes.

Must we change the webpage or the name to be able to run the log collector?

I've marked this as Solved as I've bitten the bullet and clean installed today

The install went smoothly on Samsung 9100 and no crashes, several restarts and it's fine

I'm putting it down to a Windows or driver problem causing the upgrades to fail.

I used the 26100.1742 ISO which I know worked previously, just to eliminate another possible cause. All updated to the 26100.4770

Now to spend the rest of today setting it all up again...

Update: I ran 're-install Windows' from Settings, all good

The in-place upgrade installed, restarted 3 times and back to the Desktop with no problems at all. Build 26100.4946.
I didn't keep it, I restored the backup I made this morning

Test complete, at least I know now it was more likely a driver or Windows glitch, although I have updated the BIOS since I last tried

The clean install was made with Secure boot disabled, and it still is