22449.100 will not boot

imacken said:

Thanks. From previous posts, you can see that I have:
1) removed anti-virus
2) posted the setuperr.log from Panther
3) removed all peripheral devices. (Only haven't disconnected internal drives.)
4) disconnected from internet
5) ran a SFC scan
6) submitted a whole bunch of log files as requested earlier
7) followed Kari's procedure
8) tried an in-place install from the ISO from UUDump
9) tried an in-place install from the ISO modified by Kari's process
10) uninstalled Intel SATA drivers
11) BIOS is up to date
Other things that I can't remember. Unfortunately to no avail.

Click to expand...

Gee,,. then install 10 again.

zbook said:

Volume G: was not seen using diskpart.

When Nirisoft was ran what steps were made?

It also allows you to easily change a drive letter of USB devices and remote network shares, as well as to delete a drive letter of USB device that is not plugged. You can also use DriveLetterView to export the list of all drives into text/csv/html/xml file.

Code:

Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     D   Data         NTFS   Partition    931 GB  Healthy          
  Volume 1     E   DCS          NTFS   Partition    931 GB  Healthy          
  Volume 2     F   Backups      NTFS   Partition   1863 GB  Healthy          
  Volume 3     C   Windows      NTFS   Partition    459 GB  Healthy    Boot  
  Volume 4         BOOT         FAT32  Partition    499 MB  Healthy    System
  Volume 5                      NTFS   Partition    561 MB  Healthy    Hidden
  Volume 6         Recovery     NTFS   Partition   4765 MB  Healthy    Hidden

Click to expand...

It doesn't show in DriveLetterView. The drive in question - BOOT - is a creation during this failing update. Wasn't there before all this.

imacken said:

After several months of trouble free W11, I'm very reluctant to do that. Is there not a way of telling Windows to ignore this update?

Click to expand...

You might try using Powershell to hide the update. Open an admin Powershell prompt and copy and paste the following into it. When the popup window appears, highlight the offending update and click "OK". If the update isn't listed, just click "Cancel".

$Session = New-Object -ComObject Microsoft.Update.Session
$Searcher = $Session.CreateUpdateSearcher()
$Criteria = "IsInstalled=0 or IsInstalled=0 and
deploymentaction='OptionalInstallation'"
$SearchResult = $Searcher.Search($Criteria)
$SearchResult.Updates | Out-GridView -passthru | ForEach-Object -Process {
$_.ishidden=$true}
$SearchResult.Updates | select title,ishidden
#end

Ben

Random thoughts.
It would appear the the G drive is actually the C drive, it's not been mapped by any chance? to check CMD or terminal then enter.
What does it say if you look at properties?
Try booting in safe mode and see if you can then get rid of it?

Ben Myers said:

You might try using Powershell to hide the update. Open an admin Powershell prompt and copy and paste the following into it. When the popup windows appears, highlight the offending update and click "OK". If the update isn't listed, just click "Cancel".

$Session = New-Object -ComObject Microsoft.Update.Session
$Searcher = $Session.CreateUpdateSearcher()
$Criteria = "IsInstalled=0 or IsInstalled=0 and
deploymentaction='OptionalInstallation'"
$SearchResult = $Searcher.Search($Criteria)
$SearchResult.Updates | Out-GridView -passthru | ForEach-Object -Process {
$_.ishidden=$true}
$SearchResult.Updates | select title,ishidden
#end

Ben

Click to expand...

Thank you so much, that worked! The update is now no longer showing in WU. Hopefully the next one won't have the issue.

clam1952 said:

Random thoughts.
It would appear the the G drive is actually the C drive, it's not been mapped by any chance? to check CMD or terminal

Code:

net use

then enter.
What does it say if you look at properties?
Try booting in safe mode and see if you can then get rid of it?

Click to expand...

Entering that came back with nothing. 'There are no entries on the list.'
Funny thing is, now this BOOT drive is not showing in File Explorer, whereas it was earlier, but it is still showing in DiskParInfo.

imacken said:

Entering that came back with nothing. 'There are no entries on the list.'
Funny thing is, now this BOOT drive is not showing in File Explorer, whereas it was earlier, but it is still showing in DiskParInfo.

Click to expand...

If it doesn't have a drive letter, it will not show up in File Explorer. You need to manually add a drive letter to it.

sometimes your only option buddy is reinstall windows

badrobot said:

If it doesn't have a drive letter, it will not show up in File Explorer. You need to manually add a drive letter to it.

Click to expand...

How can I do that if it doesn’t show in DriveLetterView?

imacken said:

How can I do that if it doesn’t show in DriveLetterView?

Click to expand...

imacken said:

How can I do that if it doesn’t show in DriveLetterView?

Click to expand...

Like @BunnyJ posted above...

BunnyJ said:

Change a drive letter

Learn how to change or assign a Windows drive letter by using the Change Drive Letter and Paths feature in Disk Management.

docs.microsoft.com

Click to expand...

It doesn't show in Disk Management either.

Mine shows the same because those are drives created when you install Windows.. they are associated with the primary drive(c) and don't get letters assigned,.

Mine Disk 2 is my C drive and that's where Windows is installed.

BunnyJ said:

Mine shows the same because those are drives created when you install Windows.. they are associated with the primary drive(c) and don't get letters assigned,.

Mine Disk 2 is my C drive and that's where Windows is installed.

View attachment 7266

View attachment 7267

Click to expand...

Sure, but the point is that the ‘bogus’ drive BOOT created in this failed update process is not showing at all in the list.

imacken said:

Sure, but the point is that the ‘bogus’ drive BOOT created in this failed update process is not showing at all in the list.

Click to expand...

Here,, go back to disk management and post this image plus what do you mean by 'bogus'??

It seems that the drive is corrupted.
Having multiple drives installed during an update creates all kinds of issues sometimes.
Fixing a corrupted drive is hit or miss. Sometimes it works. Sometimes it doesn't. But most of the time, reformatting it makes it readable again. But of course, you will lose everything in it.
I have a 3rd party hard drive tool called MiniTool Partition Wizard Pro which I usually use to manage my drives. When windows cannot see my drive, this tool still sees it and that's what I use to reformat corrupted drives.
There are other 3rd party tools that you can check out and use trial version to fix your hard drive issues.

Check this out.

imacken said:

I posted this in another thread, but it just got lost.

This build just won’t boot for me. Tried 3 times, same thing.
Installs OK from WU, restarts initially OK, gets to 100%, I see the new swirly graphic, then my drive light goes solid on (no flickering) and then, nothing. Just hangs.
A reboot takes me back to previous build. Looking at WU history shows a 0xc1900101 error.
First time I’ve had any issue with updates. Any ideas?

Click to expand...

After install ok from WU and re-start it, then key in command below to avoid device drivers update with administrator privilege.

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d "1" /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\OOBE" /v "DisablePrivacyExperience" /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\current\device\Update" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\default\Update" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\default\Update\ExcludeWUDriversInQualityUpdate" /v "value" /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d 1 /f

Hope it will help you!

BunnyJ said:

Check this out.

0xC1900101 – 0x20017, Installation failed in SAFE_OS phase with an error during BOOT operation

Fix Error 0xC1900101 - 0x20006, The installation failed in the SAFE_OS phase error during BOOT operation, during Windows 10 Setup.

www.thewindowsclub.com

Click to expand...

Thanks again. That was already covered a couple of pages ago. I did attach the logs at that time. Didn't mean anything to me, but maybe they might to you! I've attached them again.
Interestingly, they are not in C:\Windows\Panther for me, they are in C:\$WINDOWS.~BT\Sources\Panther. Maybe a W11 change?

jeffreywen said:

After install ok from WU and re-start it, then key in command below to avoid device drivers update with administrator privilege.

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d "1" /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\OOBE" /v "DisablePrivacyExperience" /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\current\device\Update" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\default\Update" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\default\Update\ExcludeWUDriversInQualityUpdate" /v "value" /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d 1 /f

Hope it will help you!

Click to expand...

Thanks for that. Not sure at what stage of the process these commands would be applied though.