1709 Fails to install and how to remove multiple recovery partitions?

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'.

-

zbook said:

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

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.

dalchina said:

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

Attached zip file.
Note: I also renamed the .nfo to .txt
all files are .txt files.

Hope it will cast some light on this mysterious issue.

=