New
#11
Windows update might get confused since you have disk 0 which is an MBR disk set as "Active". Open Admin command:
diskpart
select disk 0
select par 1
inactive
exit
Except for the boot disk. No data disk should be set "Active"
Windows update might get confused since you have disk 0 which is an MBR disk set as "Active". Open Admin command:
diskpart
select disk 0
select par 1
inactive
exit
Except for the boot disk. No data disk should be set "Active"
In #2 I suggested you see this:
- which indicates helpful log files, e.g. setuperr.log, setupact.log
from this:
Upgrade to Windows 10 Installation Upgrade Tutorials
And Minitool Partition Wizard -not Disk Management- will show all partitions, as I've mentioned.
1) This is a log collector that we use in another forum. Please run it and post a zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums
2) Post an image of Disk management and widen each the volume and status columns so that the letters within each row are not cut off
3) Post an image of Minitool partition wizard (free edition): MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download.com
4) Download and install: voidtools
5) Search for these Panther folders and files and post any found files (December 2017) into the thread:
C:\Windows\Panther
setuperr.log
setupact.log
Setupmem.dmp
setupapi.dev.log
BlueBox.log
Event logs (*.evtx)
C:\$Windows.~BT\Sources\Rollback
$Windows.~bt\Sources\Rollback\setupmem.dmp
$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
$Windows.~bt\Sources\Rollback*.evtx
$Windows.~BT\Sources\Panther\UnattendGC
miglog.xml
Windows\Logs\Mosetup
Ive nearly always found system service exception BSOD's to be in some way caused by anti virus programs. Best to remove this and then try again as a test :)
Thank you all - and sorry to keep you waiting.
I gave it a few other tries. Just now I tried after a clean boot
disabling all start up items
disabling all non-windows services
load system services and use original boot configuration tagged
problem still occurs.
I -assume- that this way conflicting drivers are not loaded(?)
the setuperr.log shows
-
2017-12-30 13:23:11, Error IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Rollback: Failed to create WinPE rollback directory: D:\$WINDOWS.~BT\Sources\Rollback\WinPE[gle=0x000000b7]
-
Anyway, I've probably spent more time on trying (including all the previous attempts) that a fresh install would have been quicker.
I'll forget about upgrading.
Will do a fresh install one day.
Want to really thank you all for your help
(and patience..)
FWIW... only and to more or less complete the story:
today I also tried with
1. DISM /Online /Cleanup-Image /ScanHealth, followed by chkdsk - reboot
still the same issue
2. clean boot - disabling 'load startup items', services, and disabling all items at the startup tab
still the same issue
almost certain there is no other way then to just go ahead and do a scratch install.
Well anyway ..
(no, there is no question here, just wanted to add the above, nothing more)
Sometimes an in-place upgrade repair install can help (which keeps all programs and data). But you need an iso of boot disk for your current build- which you may already have, or is available if you need it.
But it won't if the problem (and we still lack specific evidence) is related to some installed program e.g. security software.
Could AV software still interfere then when it is disabled/not loaded?
These were the only files loaded, all other were 'SYSTEM', svhost local service and network service.
=
=
Also see attached txt files.
a. they are .log files
b. the name of the file show in which folder they were residing
=
I -thought- it had something to do with Windows Kits\10 (WinPE) as that folder did not exist.
Probably renamed by Macrium Reflect
-
-
but a re-install of Windows ADK for Windows 10, version 1703 didn't solve the problem.
(after the install, again a clean boot)
also the "Windows10UpgraderApp.exe" , pretty much looking the same as "Windows10Upgrade9252.exe" didn't help.
I wonder whether I could delete the 'recovery' partitions when running a partition manager from USB
-