Windows 10: 1709 Fails to install and how to remove multiple recovery partitions?

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 *Smile

 

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

-

 

Why is this referring to D: I wonder?
2017-12-31 15:22:57, Error IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Rollback: Failed to create WinPE rollback directory: D:\$WINDOWS.~BT\Sources\Rollback\WinPE[gle=0x000000b7]

CDownloadDUUpdates:*BiggrinoExecuteInternal: Did not find hard disk space needed, when update cab files will not be extracted. This is unexpected! hr = 0x8000ffff
2017-12-31 12:16:57, Error SP CSetupPlatform:*BiggrinownloadDynamicUpdates: Failed to download updates. Error: 0x8000FFFF

- this strongly suggest you attempt the upgrade without allowing updates during the upgrade.

Note this is a practice that simplifies the process significantly.

 

As for the WinPE thing: beats me ... I have nothing like that on the D-drive, which are all non-office applications and data

I also saw the 'did not find hard disk space needed'
which is a bit curious as there is still 335GB left.

The last two attempts I did without downloading 'important updates'.

-

 

Please look for these files:
setupact.log (not in the above)
setuperr.log (see if there is a larger file)

Run this log collector for troubleshooting:
BSOD - Posting Instructions - Windows 10 Forums
Language - Add, Remove, and Change in Windows 10 General Tips Tutorials

 

I suggest you try disconnecting all other disks than your system disk- or at least that which appears as Disk 0.
With the advent of the Creator's build, MS told me they changed their disk numbering scheme from 1-9 to 0-9. I have two disks - and until the Anniversary build, all was well. Come the Creator's build, the upgrade went smoothly- but the Advanced startup options failed oddly. The problem applied only in upgrading- a clean install of 1703 or 1607 was fine.

This might explain why it seems Windows is attempting to use the wrong disk when upgrading... I don't know.

Note this does not seem to affect the majority of people,

You can try deleting the content of
%temp%
and
C:\Windows\SoftwareDistribution\Download

and
Reset Windows Update in Windows 10 Windows Update Activation Tutorials

 

Happy New Year to you!

Thanks for the above.

ehm.. which one ? there are quite a number of them




-

as for the dm_log_collector: I hesitate about that one - not sure if it is giving away privacy info.
also my AV scanner warned me (_zipit.vbs) so I quarantined it.

-

 

The logs should not be collecting private.
There are 2 options on the DM log collector. The Beta version is on the bottom of the page:
BSOD Crashes and Debugging - Windows 10 Forums
If you visit the BSOD forum you will be able to see the log files that it collects or you can see them on the computer's desktop before making the zip.
It should collect: msinfo32, dxdiag. drivers. mini dumps, hosts, install, uninstall, services, startup, event viewer logs, etc.

For the Panther logs needed see post #15.
For the posted we will look at all.

 

Happy New Year to you too!

Thanks.
If the disk numbering is the issue, Microsoft is making users lives really tough...

This may(??) explain the "D:" in the setuperr.log

--
2018-01-01 09:20:41, Error IBSLIB
OSRollbackService::CBootFilesRestoreCheckpoint::Rollback: Failed to create WinPE rollback directory: D:\$WINDOWS.~BT\Sources\Rollback\WinPE[gle=0x000000b7]
--

Unsure how to solve that without having to detaching the drive...
-in BIOS ?
-using a partition manager?

Thing is that all a lot of files are changed on C:\ so I can only but assume that windows detects this drive (partition) as the one Windows resides on.
further attempts:

1.
- uninstalled security software
- delete: %temp% and Software Distribution\Downloads
- clean boot (selective startup: load system services+original boot configuration, services: disabling all non-windows services, disabling running startup items)
same issue

2.
- uninstalled security software
- uninstalled Samsung Magician - there were some threads where Samsung Magician was mentioned to be the cause
(see: Windows 10 Insider Preview Build 16215 issues | Borns Tech and Windows World and
Update from 16199 to 16215 fails - 0xC1900101 - 0x30017 - Microsoft Community)
- delete the temp and download stuff
- clean boot
same issue

=



=

 

This is a 3rd method to collect the logs for troubleshooting:

1) BSOD - Posting Instructions - Windows 10 Forums

2) log collector v2-beta06.zip

3) Open administrative command prompt and copy and past the whole command:

Code: md "%USERPROFILE%\Desktop\CollectedFiles"&wmic /output:"%USERPROFILE%\Desktop\CollectedFiles\hotfix.txt" qfe list full /format:table&copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\CollectedFiles"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\CollectedFiles\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.tmp"&findstr /v "Owner." "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.tmp" > "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.txt"&del "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.tmp"&driverquery /v > "%USERPROFILE%\Desktop\CollectedFiles\drivers.txt"&msinfo32 /nfo "%USERPROFILE%\Desktop\CollectedFiles\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\CollectedFiles\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\CollectedFiles\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\CollectedFiles\installed.txt"&net start > "%USERPROFILE%\Desktop\CollectedFiles\services.txt"&sc query type= driver state= all > "%USERPROFILE%\Desktop\CollectedFiles\driver_status.txt"&sc query type= service state= inactive > "%USERPROFILE%\Desktop\CollectedFiles\inactive_services_status.txt"&sc query type= service state= all > "%USERPROFILE%\Desktop\CollectedFiles\all_services_status.txt"&REM wmic service list full /format:htable >%USERPROFILE%\Desktop\CollectedFiles\service.html&REM wmic /output:%USERPROFILE%\Desktop\CollectedFiles\nics.html nicconfig list /format:hform[/quote]