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

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.

=

 

For all of these steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.

1) in the left lower corner serach type: dxdiag > open each page > allow a few minutes for it to load > post into the thread
2) type: msinfo32 > save as NFO > post into the thread

3) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

4) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

5) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
> on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
> on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

6) In the left lower corner search type services > open windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread

7) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
Resplendence Software - WhoCrashed, automatic crash dump analyzer
8) Click analyze > look for dead or deaddead in the results > post the results into the thread
9) Run the DM log collector after all of the above steps and post a zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums
BSOD - Posting Instructions - Windows 10 Forums

10) Run HDTune: HD Tune website
to check the health,
scan for errors, no quick scan but full scan
run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 General Tips Tutorials

11) Open administrative command prompt and type or copy and paste:
12) sfc /scannow
13) dism /online /cleanup-image /restorehealth
14) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

15) chkdsk /x /f /r
This may take many hours so plan to run overnight
16) Use the information in this link to find the chkdsk report in the event viewer and post the results into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

17) Backup all files on the computer
18) Make a backup image using Macrium or if you are currently using Macrium update the image
Macrium Software | Macrium Reflect Free
19) Make a brand new restore point
20) Read this information on windows driver verifier (do not use the tool until it is communicated in the thread)
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

21) Open device manger > click view > show hidden devices > look for any row with an icon that is a yellow triangle with a black exclamation mark > post images into the thread.

22) Uninstall Emsisoft AV using the uninstall tool:
How can I completely uninstall an Emsisoft Product? - Powered by Kayako Help Desk Software

23) Uninstall Malwarebytes using control panel.
24) Make sure Windows defender is on.

 

Sorry for being late in posting the solution...

I finally got Windows 1709 installed.

To shortly bring into memory:
- in my case the existing Windows was installed on DISK 1
- upgrading to 1709 was not possible
- I wrongly assumed that it did not matter on which disk Windows is being installed
so each install failed as apparently Windows 'demands' being installed on DISK 0

I went on as follows:

1) In BIOS I disabled the SATA port of DISK 1
2) Reboot
3) Diskmgmt showed that DISK 1 (SSD with Windows) became DISK 0
4) Boot from USB (created by Media Creation Tool)
5) Then selected "Repair your computer" (do not select 'Install now')
6) Click "Troubleshoot"
7) Click "Command Prompt"
8) Then execute the DISKPART instructions found on "UEFI/GPT-based hard drive partitions" UEFI/GPT-based hard drive partitions
(see at the bottom)


diskpart
list disk
rem make sure to select the correct disk number, in most cases for Windows disk 0
select disk 0
cleanconvert gpt
create partition efi size=100
format quick fs=fat32 label="System"
assign letter="S"
create partition msr size=16
create partition primary
shrink minimum=500
format quick fs=ntfs label="Windows"
assign letter="W"
create partition primary
format quick fs=ntfs label="Recovery tools"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
exit
exit

9) Reboot and launch setup from USB
10) Select "Install now" this time and select the proper partition (named "Windows")





Note that after Windows install and after re-enabling SATA-port of DISK 1 (in BIOS),
the Windows HDD changes back from DISK 0 to DISK 1 again.

-

 

Well done- Interesting... and relevant in a way to me- basically similar hardware (SSD + SSHD) and my SSD is Disk 1.

However, I CAN upgrade successfully (1607 -> 1703, 1703-> 1709) BUT since 1703 I have a problem with my Recovery partition- a straight upgrade leaves it impossible to use advanced recovery options.

My suspicion as per my earlier post about a change in MS's disk numbering schema is that's the impact of that.

So if I were to follow similar steps I could possibly resolve that.

 

FWIW...
Also note that IF(!) DISK 1 remained in place, and even after all the DISKPART stuff above, a clean Windows install was nót successful...
Always ending up with the same BSOD and Windows setup error 0x1900101 - 0x30017
"The installation failed in the FIRST_BOOT phase with an error during BOOT operation"
At least, not with me.

That said, in this scenario, one has to be a real 'expert' to install Windows ...*Smile

 

I always keep Windows on Disk "0" partition "C"; I don't know why one wouldn't.
If Windows is on Disk "0" partition "C" and all other drives are unhooked, I don't believe their will be a problem except for the time it takes to download and install a Upgrade.

Jack

 

I clean installed Win 10 on this laptop (SSD + HDD) as 1511. When I got to 1703 I found a problem, and realised then my SSD was Disk 1 as seen by Disk Management. No choice, no control.

The disk numbers are seen differently too in installing Windows by builds 1607 and 1703. (When choosing partitions to delete).

But MS changed their numbering scheme internally from 1-9 to 0-9 (an MS tech guy told me) with 1703. Can't say I fully understand it, but that's when I noticed the difference.

 

Thanks for the info dalchina.

I have never had a laptop, sorry for not understanding. Now I do.

What does Disk Management show now?

Jack

 

-from 1703 I've had to clean install 1607, then copy C: from my CU or FCU over the newly created C: then let automated repair run - and this time I had to run reagentc /disable & /enable to have recovery options fully available. Weird.

I just wonder how long I'll get away with it. There's a long thread about this when we tried to sort this out before I discovered the disk number difference when clean installing, quite by chance. Maybe it would help if I were to disconnect my data disk, however there are a couple of things that make that not so straightforward.

 

I had my pc built, based on the components I had chosen. I asked the shop to keep 1 SATA cable loose so I could connect a new, spare 2TB HDD. That HDD was connected to SATA port 8, but in Windows it became DISK 1, whereas in fact SATA port 1 was/is the SSD.
So, SATA port 8, instead of becoming DISK 8 or whatever. overruled DISK 0, placing itself on top of the list..
Bottomline I think Microsoft should sort this out, i.e. allow install on a different disk#
Probably there are many more people with Windows on DISK 1 and potentially they will head for issues when re-installing Windows.

 

@ dalchina.

Can the unallocate on Disk "0" be deleted? What is on it?

Maybe Mini Tool would be helpful.

From my computer.





Jack

 

That's part of the basic disk structure. It's not a partition I've created.