0xC1900101-0x20017 trying to upgrade an HP Compaq Pro 6300 MT to Windows 22H2

Topic

New Reply

[SupremeLaW]

regular Windows Updates are working fine on our HP Z240 workstations.

At the MS web page for Windows Update Assistant …

https://www.microsoft.com/en-us/software-download/windows10

I ran Windows10Upgrade9252.exe
-and-
I ran MediaCreationTool22H2.exe

Windows Update error also persists: 0xC1900101-0x20017 (NOT FIXED)

I’m now trying to upgrade an HP Compaq Pro 6300 MT to Windows 10 22H2, but all attempts are failing with the same error.

The first half of that error message also results from trying standard Windows Updates too.

The majority of informed opinions suggest a “driver error” of some kind, but there are not any missing drivers in Device Manager.

THIS IS A TOUGH ONE, and please appreciate my frustration:

I’ve been at this all day today, and I’m not any closer to a solution.

Thanks in advance for any effective solutions and/or useful suggestions.

One PC User suggested GIVING UP and keeping an older Windows 10 version running.

• This topic was modified 1 year, 12 months ago by SupremeLaW.

Reply | Quote

Replies

the DriverEasy third-party software finds 2 drivers that do not show up in Device Manager.

Reply | Quote

Just because you don’t have the very latest drivers does not mean you will have problems – contrary to the reports from 3rd party “driver updaters”.

I would try an install over the top.
Got a misbehaving Windows 10? reinstall

cheers, Paul

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Re: “Just because you don’t have the very latest drivers does not mean you will have problems”

Yes, for that reason, I’m inclined to GIVE UP, as one Prosumer recommended after getting the same error code during Windows Update.

The other reason is that I have several USB devices connected to this PC, e.g. a USB 3.0 5GbE dongle, APC UPS PowerChute cable and a USB 3.0 add-in-card that controls 2 external SSDs.

And, having done so much trial-and-error for decades, I already know how much time can be required of that method, and I’m simply not willing to do more trials-and-errors this time — to do Microsoft’s job for them free of charge.

I must confess that I have maintained some distance from Windows OS internals for many years now.

If their system software issues a single obscure error code that occurs for a multitude of different reasons, AT A MINIMUM their software should be coded to disclose more relevant information about “the problem” it detects.

For example in this case, if the problem is some “device driver”, MS programmers should be documenting that problem with much more details, e.g. in a LOG file of some kind.  I searched the Windows Event Viewer database, without any success.

Here, Windows 10 is effectively saying:  YOUR PROBLEM IS #$%#$##%%# and then it reverts back to an older Build, after taking more than an hour to reach that outcome.

Sorry for the rant:  Susan Bradley has been recommending Windows 10 22H2.

I have been half-expecting this sort of nonsense, after enabling WinUpdateStop for many years.  Windows 10 has been mostly trouble-free for me, as long as Windows Update remained DISABLED on this PC.

 

 

Reply | Quote

What is the current Windows 10 version (run winver) ?

1 user thanked author for this post.

SupremeLaW

Reply | Quote

There was also this longer error message:

“The installation failed in the SAFE-OS phase with an error during BOOT operation.”

WINVER says:  Windows 10 Pro, Version 1909, OS Build 18363.1256

Reply | Quote

Windows Update History

Reply | Quote

According to Microsoft’s Windows 10 upgrade resolution procedures page, 0xC1900101 – 0x20017 is a SafeOS boot failure typically caused by drivers, non-Microsoft disk encryption software or hardware failure.

Recommendations:

• Disconnect all peripheral devices connected to the system, except for the mouse, keyboard and display, and try the update again.

• Update or uninstall the problem driver(s).

It also includes a link for Windows Vista, Windows 7, Windows Server 2008 R2, Windows 8.1, and Windows 10 setup log file locations that contains a long list of various log file locations you can check that “might” help isolate the specific driver causing the problem.

You could also visit the HP Customer Support – Software and Driver Downloads site and click the “Let HP detect your product” option to see if it finds any newer drivers for that system.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Many thanks!

Yes, I have tried searching inside a few of those setup log files.

I was able to find occurrences of “0xC1900101” (without quotes) BUT

there was no other text that helped to isolate the problem “driver” (if any).

I’m writing this on the problem PC, and there are no other apparent problems.

So, given the cost-benefit of spending hours and hours to fix an update defect that is not showing up anywhere else, BEST WAY for now is to just GIVE UP!

I know that runs counter to a policy of “staying up-to-date”, but it’s a practical solution.

Down the road, I do intend to migrate my production work e.g. website maintenance, to a newer HP Z240, and the 22H2 updates installed AOK on that workstation.  It’s also running fine on a native M.2 NVMe SSD that is installed in a dedicated M.2 socket on the Z240’s motherboard.

This photo is upside down:  at the top see the Samsung 960 Pro:

Reply | Quote

I do have a brand new / never used OEM DVD disc of

Windows 10 Pro 64-bit version 21H2

purchased at Newegg in August 2022.

I have no experience “overwriting” an existing Windows OS with that version 21H2.

During routine Windows SETUP, is there an option to install that version 21H2 on top of the existing OS version 1909 files — BUT withOUT deleting existing programs?

I have noticed folder “Windows.old” has been created in the C: system partition, and I saw a message stating it would be deleted after 10 calendar days — first week of June 2023.

e.g. I have already installed a licensed copy of MS WORD and it would be ideal if 21H2 preserved all existing programs and files.  I would rather avoid needing to re-install all third-party software again.

Reply | Quote

Be sure you have a full disk image before you start.

How to do an upgrade over the top.

Boot from Win 21H2.
Insert the 22H2 install media on a USB stick OR mount the 22H2 ISO using Explorer.
Navigate to the USB stick OR ISO
Run setup.exe on the install media from within the running Win 21H2.
It will give you the option to “keep your data and programs,” ” keep your data only,” or keep nothing.
Choose “keep your data and programs”
Follow the instructions.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Thanks.

However, I need to upgrade from Windows 10 version 1909 to version 21H2 on the DVD I purchased from Newegg.

I purchased that DVD last August 2022.

p.s.  My current theory is that the RAID controller driver is the culprit:

later today I intend to see if there is a more recent driver at Highpoint’s website.

Device Manager says the driver currently installed is dated 2015.

 

Reply | Quote

It should work the same from 1909 to 21H2 (provided the driver problem doesn’t get in the way). Run setup.exe from within the running existing system.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

running setup.exe on the OEM DVD disc with Windows 10 Pro 21H2 did NOT work:

I’m getting the same 2 error messages that I got after trying both options in Windows Update Assistant:

“The installation failed in the SAFE-OS phase with an error during BOOT operation.”

“We’ve set your PC back to the way it was right before you started installing Windows 10.”

A trial-and-error approach would now require:

(1) removing the USB cable to the APC UPS

(2) removing the USB cable to the HP LaserJet printer

(3) removing 2 USB cables each with external SSDs attached

(4) removing the USB 3.0 to 5GbE dongle

(5) connecting the integrated 1GbE controller to a 1G LAN

(6) removing the Highpoint 620 controller

(7) removing the Highpoint 2720SGL controller

(8) removing a PCIe x1 USB 3.0 adapter

Then, I would need to restore C: that is now hosted by the 2720SGL controller to a JBOD SSD wired directly to a motherboard SATA port.

Only then would I be able to start isolating which “driver” is most likely the culprit.

And, there is no guarantee that the setup.exe program on the OEM disc will not stumble again, after finding a device driver it doesn’t like, EVEN IF the corresponding device is removed.

As I said earlier, GIVING UP is a very practical alternative; and, I can easily migrate all necessary third-party software to an HP Z240 that did install all Windows Updates AOK.

Thanks again for your helpful suggestions.

In my younger years, I might have accepted this challenge and burned a lot of midnight oil.  But, being retired, I really don’t need to do so now.

Reply | Quote

Re:  “Run setup.exe from within the running existing system.”

I’ll remember to do that.  MANY THANKS for that tip!

FYI:  I just triple-checked the device driver for our Highpoint RocketRAID 2720SGL:

it’s currently hosting C: on a RAID-0 array of multiple WDC 2.5″ SSDs, which have worked perfectly for several years.

Current theory now is that Windows Update and Windows Update Assistant both have a problem with the age of the currently installed 2720SGL controller driver e.g. possibly “not signed” etc.

I just now downloaded the latest device driver for that controller, to compare with the driver now installed and running AOK.

The latest driver files have not changed after I first migrated C: to that RAID-0 array:

NOTE WELL:  “04/15/2015 05:49 PM 633,072 272x_1x.sys”

That .sys is the exact same size, and same date, as the driver installed at C:\Windows\System32\drivers

Here’s the output of a DIR command in that sub-folder with the latest driver files:

Volume in drive E is Paul27-E
Volume Serial Number is BBAF-6600

Directory of E:\Highpoint.RocketRAID.2720SGL.Win10\driver2\x64

05/22/2023 01:18 PM <DIR> .
05/22/2023 01:18 PM <DIR> ..
04/15/2015 05:49 PM 10,332 272x_1x.cat
04/15/2015 05:26 PM 2,716 272x_1x.inf
04/15/2015 05:49 PM 633,072 272x_1x.sys
3 File(s) 646,120 bytes
2 Dir(s) 888,846,811,136 bytes free

Reply | Quote

FYI:  the file WindowsUpdate.log must now be written by a PowerShell command that converts EventViewer format into plain ASCII.

I’ve located “0xC1900101” and attached both contexts to this post.

(I got a serious error message that blocked me from pasting that ASCII here.)

In both contexts, find:

Update status code is 0xC1900101

 

Reply | Quote

WindowsUpdate.log_.excerpts

Reply | Quote

Has Microsoft perhaps offered a single-purpose utility to verify whether or not all installed drivers are compatible with pending Windows Updates and/or upgrading to newer versions of Windows 10?

A stand-alone program would be ideal, which could be executed BEFORE doing anything else.

It occurs to me that the setup.exe program on the OEM DVD of Windows 10 21H2 should perform such a drivers verification UP FRONT and immediately inform the User of any driver problems it detects …

… RATHER THAN requiring the User to stare at a monitor for 2 hours, ONLY TO BE TOLD the installation failed and the entire system was ROLLED BACK to “the way it was right before the User started installing Windows 10.”

Reply | Quote

I did more searching with BING instead of Google, and a few results strongly recommended close scrutiny of the motherboard’s integrated SATA ports.

After following that advice, I did confirm that a slow 3.5″ WDC “Blue” HDD was cabled to the integrated eSATA port (circle 10), and the ODD was cabled to a standard SATA-II port (circle 9).

One helpful clue was that the 3.5″ WDC “Blue” HDD was showing up as a “removable device”, which would usually apply to eSATA external storage enclosures.

That implied that the cabling was backwards.

Also, the eSATA port (circle 10) is stated to be compatible with a 2nd Optical Drive, so that told me that my one ODD should be cabled to that eSATA port on the motherboard.

So, I’ve switched those around:  now, the HDD is cabled to the standard SATA-II port (circle 9), and the ODD is cabled to the eSATA port (circle 10).

After rebooting, the 3.5″ WDC “Blue” HDD is no longer listed as a “removable device”, so that was a little confirmation I’m on the right track now.

Time permitting, I’ll try again installing my OEM DVD of Windows 10 Version 21H2.

See inside red rectangle here:

Reply | Quote

I just noticed something else:

Note at circle 8 where it says: “2nd Optical Drive if an eSATA Adapter Cable exists”

That implies the eSATA port could be wired to a slot adapter, to provide 1 x eSATA port to the rear I/O panel.

With the eSATA port wired to a slot adapter, then the ODD would need to be wired to SATA2 (1st Optical Drive) or SATA1 (2nd Optical Drive).

In our workstation, we have 2 x SSDs, 1 x HDD, and 1 x ODD, now wired as follows:

SATA0 = SSD @ 6G

SATA1 = SSD @ 3G

SATA2 = HDD @ 3G

ESATA = ODD

Reply | Quote

Here’s very possibly where the problem originated, simply because I was following these instructions.

There were no instructions specifically for the combination of 3 x SATA drives, only 1 ODD and no eSATA adapter cable (to add 1 x eSATA port at the rear I/O panel).

I wired the only ODD to SATA2, i.e. “the first SATA optical drive” and that necessarily required the third SATA drive to be wired to the ESATA port.

See the text with red underlines:

 

Reply | Quote

Another trial / another error

Reply | Quote

Imagine my JOY after reading this today:

1 user thanked author for this post.

geekdom

Reply | Quote

Well, that’s just not friendly.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

SupremeLaW

Reply | Quote

What has generated mid-level FURY in me is this discovery:

many Windows “experts” have written that the error message I continue to get, after total ROLL-BACK, is usually a “driver problem”. 

And, some of those experts point to a log file in C:\Windows\Panther\ where there is supposed to be enough information to identify the problem driver.

So, I looked for that error code in those log files:  0xC1900101-0x20017

I believe I already posted the attached, but I’ll repeat it.

WindowsUpdate.log_.excerpts

Reply | Quote

the full log file is about 800K (see attached)

windowsupdate.log_

Reply | Quote

SetupDiag

https://learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag?source=recommendations

 

Reply | Quote

Ran SetupDiag.exe

following is the relevant excerpt (full log is attached)

SetupDiagResults

Error: SetupDiag reports rollback failure found.
Last Phase = Finalize
Last Operation = Remove System Restore checkpoints
Error = 0xC1900101-0x20017
LogEntry:

Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.

Last Setup Phase:
Phase Name: Finalize
Phase Started: 5/24/2023 3:14:07 PM
Phase Ended: 5/24/2023 3:14:12 PM
Phase Time Delta: 00:00:05
Completed Successfully? True


Last Setup Operation:
Operation Name: Remove System Restore checkpoints
Operation Started: 5/24/2023 3:14:12 PM
Operation Ended: 5/24/2023 3:14:12 PM
Operation Time Delta: 0:00:00:00.0000000
Completed Successfully? True

Reply | Quote

Unable to open log or download file. “403 Forbbidden” error.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

I believe that error message results from a security policy enforced by this Forum.

I’ll try to paste the first half of that log here:

[BEGIN QUOTE]

Matching Profile found: FindRollbackFailure - 3A43C9B5-05B3-4F7C-A955-88F991BB5A48
SetupDiag version: 1.6.2107.27002
System Information:
Machine Name = DESKTOP-KSPU6U0
Manufacturer = Hewlett-Packard
Model = HP Compaq Pro 6300 MT
HostOSArchitecture = x64
FirmwareType = PCAT
BiosReleaseDate = 20190410000000.000000+000
BiosVendor = Default System BIOS
BiosVersion = K01 v03.08
HostOSVersion = 10.0.18363
HostOSBuildString = 18362.1.amd64fre.19h1_release.190318-1202
TargetOSBuildString = 10.0.19041.2780 (vb_release_svc_prod2.230213-1721)
HostOSLanguageId = 
HostOSEdition = Professional
RegisteredAV = Windows Defender
FilterDrivers = FileInfo
UpgradeStartTime = 5/24/2023 2:55:56 PM
UpgradeEndTime = 5/24/2023 3:14:20 PM
UpgradeElapsedTime = 00:18:24
CV = NYL1zUKGh0OivUeb
ReportId =

[END QUOTE]

Reply | Quote

file name “SetupDiagResults.log” is attached

Reply | Quote

same error:  sorry / it appears to be a Forum security policy

But, above I’ve posted both the first half and the second half,

so combine the two for the full “SetupDiagResults.log” file (plain ASCII)

Reply | Quote

This User’s experience is almost identical to my experience:

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/trying-to-upgrade-from-windows-10-1909-to-20h2-and/e59f313b-63e4-480c-a3cf-e197d82a482f?page=2

Trying to upgrade from Windows 10 1909 to 20H2 and it fails. I was advised here to use the Media Creation Tool 20H2 because Windows Update says it’s “managed by your organization”

[BEGIN QUOTE]

So, Sumit, one of the fellas in this group, advised me to download and run the "Media Creation Tool20H2". Which I did. And I get the following...

We couldn't install Windows 10
We've set your PC back to the way it was right before you started installing Windows 10.

0xC1900101 - 0x20017
The installation failed in the SAFE_OS phase with an error during BOOT operation

I'm concerned because I had received a message that my version of W10 will become unsupported. Duh! It appears to me that it's already unsupported, as no solutions are forthcoming from Microsoft.

Why can't Microsoft provide a solution to this issue? I have lots of expensive software on this machine, which I don't want to lose. If I'm even able to re-install it, I can see it taking me a week or more to do so, even if I don't have to deal with the software vendors.

I tried removing all of the USB devices, etc. Nothing works.

So, is there a way around this issue? This is killing me.

Is there some way to reset the policy to a default or "whatever" to accommodate the update?

PLEASE HELP ME!

Thanks,

Steve

[END QUOTE]

Reply | Quote

I omitted the “date created” for that excerpt immediately above:

17 May 2021 09:52:25 AM

This is May 2023.  (I just checked Internet date and time.)

This problem has remained unsolved by Microsoft for two (2) full years.

But, now we are being told that MS intends to FORCE us to upgrade to Windows 10 22H2.

Reply | Quote

MS now intends to FORCE 22H2 on everyone!

saw this earlier today at msn.com

Reply | Quote

Based on some Googling of your driver error code I discovered that Virtualization Technology (VTx) can sometimes cause this problem because, if it’s enabled in the BIOS, it forces Windows to install a driver that “may” be incompatible with the new update. And because the VTx driver isn’t for an external device, disconnecting all your peripherals doesn’t get rid of the error!

The setting “should” be in your 6300 MT BIOS under Security > System Security > Virtualization Technology (VTx)

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Thanks for that tip.

In the past, I’ve had trouble accessing the motherboard BIOS on this PC.

I think that problem was due to my KVM switch:  I did eventually did access the BIOS with a USB keyboard that plugged straight into a USB 2.0 port on the front panel.

 

Q:  is there a way to confirm that VTx is enabled withOUT accessing the motherboard BIOS?

 

Reply | Quote

Windows 10 Task Manager reports “Virtualization:  Disabled”

CPU-Z does say VT-x instructions are supported by the Intel Core i5-3470 CPU.

Reply | Quote

Re:  “And because the VTx driver isn’t for an external device, disconnecting all your peripherals doesn’t get rid of the error!”

Yes, I considered that possibility VERY SERIOUSLY.  🙂

After building this workstation up slowly and carefully, over many months, to a fully functional machine, I am not about to tear it down merely because MS now intends to FORCE 22H2 on everyone.

This PC in its current configuration does everything I need, very reliably, with Windows 10 version 1909.  I’m using it to write this.

One of the 2.5″ SSDs now installed is accessible at the front panel, where I’ve added an Icy Dock enclosure in an empty 3.5″ drive bay.  That 2.5″ SSD bay is already wired to the SATA0 6G port on the motherboard.

So, I can remove that older SSD, attach it to an external USB 3.0 adapter, and Migrate OS to a new WDC 2TB “Red” SSD after I install it in that Icy Dock enclosure.

Hopefully, all this trouble will preserve all existing third-party software etc.

 

Reply | Quote

Boatload of this error:
https://duckduckgo.com/?t=ffab&q=0xC1900101-0x20017&ia=web

I’ve found that technical sites, such as this one, usually avoid boilerplate responses:
https://social.technet.microsoft.com/wiki/contents/articles/35608.windows-10-troubleshooting-error-0xc1900101-020017-installation-failed-in-safe-os-phase-with-error-during-boot-operation.aspx

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

SupremeLaW

Reply | Quote

MANY THANKS!

Yes, I have been suspecting our RAID controller, which hosts C: .

Highpoint model 2720SGL

The clue was that a brand new OEM DVD of Windows 10 21H2 also failed the EXACT SAME WAY!

So, the following is something I understand and CAN DO, time permitting (SEE “Resolution” BELOW).

I’ll probably purchase a new WDC 2TB 2.5″ “Red” SSD, wire it to the motherboard SATA0 port (6G / SATA-III), and use Migrate OS in our Partition Wizard software.

The latter should preserve all third-party apps etc.; and, testing simply requires changing the “boot drive” in the motherboard BIOS.

Then, if Windows Update Assistant completes successfully after writing to that WDC “Red” hosting an updated C: , THEN I should be able to create a drive image of that updated OS and then restore that drive image back to the RAID-0 array.

[BEGIN QUOTE]

Resolution

Move OS drive from RAID controller to SATA AHCI controller.

Upgrade the windows 7 to windows 10.

Update RAID controller driver from dell website “https://downloadcenter.intel.com/download/25393/Intel-RSTe-AHCI-SCU-Software-RAID-driver-for-Windows Jump -“

Switch back the controllers for OS drive.

Or, we can inject the raid driver in install.wim, in advance, check here Jump for procedure.

[END QUOTE]

1 user thanked author for this post.

geekdom

Reply | Quote

I just remembered that we have a nearly identical HP Compaq Pro 6300, but it’s a Small Form Factor (“SFF”).

It’s the exact same HP model 339A.

It also hosts C: on a Highpoint RocketRAID 2720SGL.

And, the good news for that PC is that Windows 10 22H2 updated AOK the first time:

Reply | Quote

Since you have two “basically identical” PC’s, finding the problem driver(s) just became a lot easier.

Use the following powershell command to generate a list of the drivers/versions on each PC.

Get-WmiObject Win32_PnPSignedDriver | DeviceName,DriverVersion

Note: the powershell window must be wide enough or it won’t display the whole version# (I’d suggest at least 136 characters.)

Then simply compare the drivers/versions between the two PC’s to determine which one’s are “different” on the 1909 PC you can’t update and then update them to the same version as the 22H2 PC and try to update 1909 to 22H2 again.

FYI, if the 1909 PC is using a driver the 22H2 PC isn’t using, and it’s not required for some particular function on the 1909 PC, delete it!

One gottcha with this powershell command… it only displays “signed” drivers so, if your system is using any “unsigned” drivers, they won’t be shown!

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Yes, some of the add-in cards required UNsigned drivers.

Thanks for that PowerShell tip.

Reply | Quote

Trying that PowerShell command, I get this error message:

Reply | Quote

My bad, I didn’t include the Select part of the command!

It should’ve been:

Get-WmiObject Win32_PnPSignedDriver | Select DeviceName,DriverVersion

BTW, I didn’t include the “Description” option because, at least on my system, it’s exactly the same as DeviceName!

1 user thanked author for this post.

SupremeLaW

Reply | Quote

both of these PS commands appear to be working:

gwmi win32_PnpSignedDriver | Select Description, DriverVersion

gwmi win32_PnpSignedDriver | Select DeviceName, DriverVersion

Reply | Quote

I re-directed the output to a .txt file, BUT as you say, this list may only show SIGNED drivers, NOT any UNsigned drivers:

Description DriverVersion 
----------- ------------- 
Local Print Queue 10.0.18362.1 
Local Print Queue 10.0.18362.1 
Local Print Queue 10.0.18362.1 
Local Print Queue 10.0.18362.1 
Local Print Queue 10.0.18362.1 
Local Print Queue 10.0.18362.1 
WAN Miniport (Network Monitor) 10.0.18362.1 
WAN Miniport (IPv6) 10.0.18362.1 
WAN Miniport (IP) 10.0.18362.1 
WAN Miniport (PPPOE) 10.0.18362.1 
WAN Miniport (PPTP) 10.0.18362.1 
WAN Miniport (L2TP) 10.0.18362.1 
WAN Miniport (IKEv2) 10.0.18362.1 
WAN Miniport (SSTP) 10.0.18362.1 
Generic software device 10.0.18362.1 
Generic software device 10.0.18362.1 
Generic software device 10.0.18362.1 
Generic software device 10.0.18362.1 
Remote Desktop Device Redirector Bus 10.0.18362.1 
IWD Bus Enumerator 4.5.71.0 
Plug and Play Software Device Enumerator 10.0.18362.329 
Microsoft System Management BIOS Driver 10.0.18362.1 
NDIS Virtual Network Adapter Enumerator 10.0.18362.1 
Microsoft Basic Render Driver 10.0.18362.329 
ACPI Fixed Feature Button 10.0.18362.267 
Microsoft Windows Management Interface for ACPI 10.0.18362.1 
ACPI Thermal Zone 10.0.18362.267 
ACPI Thermal Zone 10.0.18362.267 
ACPI Fan 10.0.18362.267 
ACPI Fan 10.0.18362.267 
ACPI Fan 10.0.18362.267 
ACPI Fan 10.0.18362.267 
ACPI Fan 10.0.18362.267 
Intel Processor 10.0.18362.1049
Intel Processor 10.0.18362.1049
Intel Processor 10.0.18362.1049
Intel Processor 10.0.18362.1049
System board 10.0.18362.267 
ACPI Power Button 10.0.18362.267 
Motherboard resources 10.0.18362.267 
System board 10.0.18362.267 
Intel(R) 7 Series/C216 Chipset Family SMBus Host Controller - 1E22 10.1.1.38 
CD-ROM Drive 6.3.9600.16384 
Disk drive 10.0.18362.1350
Disk drive 10.0.18362.1350
Disk drive 10.0.18362.1350
Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller 13.1.0.1058 
Trusted Platform Module 1.2 10.0.18362.1316
Communications Port 10.0.18362.1 
Numeric data processor 10.0.18362.267 
Motherboard resources 10.0.18362.267 
Microsoft PS/2 Mouse 10.0.18362.1 
Standard PS/2 Keyboard 10.0.18362.1 
Motherboard resources 10.0.18362.267 
Motherboard resources 10.0.18362.267 
System timer 10.0.18362.267 
System CMOS/real time clock 10.0.18362.267 
Motherboard resources 10.0.18362.267 
Programmable interrupt controller 10.0.18362.267 
High precision event timer 10.0.18362.267 
Legacy device 10.0.18362.267 
Direct memory access controller 10.0.18362.267 
Intel(R) Q75 Express Chipset LPC Controller - 1E48 10.1.1.45 
Intel(R) 82801 PCI Bridge - 244E 7.0.0.1011 
Generic USB Hub 10.0.18362.1110
USB Root Hub 10.0.18362.1 
Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E26 9.3.0.1030 
IDE Channel 10.0.18362.1533
IDE Channel 10.0.18362.1533
Standard Dual Channel PCI IDE Controller 10.0.18362.1533
HighPoint RCM Device 1.3.12.606 
Disk drive 10.0.18362.1350
Disk drive 10.0.18362.1350
RocketRAID 620 SATA Controller 1.3.12.606 
Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 5 - 1E18 10.1.1.45 
Disk drive 10.0.18362.1350
VIA USB Mass Storage Device (0711) 6.1.7600.4002 
Disk drive 10.0.18362.1350
VIA USB Mass Storage Device (0711) 6.1.7600.4002 
VIA USB 2 Hub 6.1.7600.4903 
VIA USB 3 Root Hub 6.1.7600.4903 
VIA USB eXtensible Host Controller 6.1.7600.4903 
Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 1 - 1E10 10.1.1.45 
Intel(R) Display Audio 6.16.0.3208 
Audio Endpoint 10.0.18362.1 
Realtek High Definition Audio 6.0.9239.1 
High Definition Audio Controller 10.0.18362.693 
APC UPS 1.2.0.0 
American Power Conversion USB UPS 10.0.18362.175 
Generic USB Hub 10.0.18362.1110
USB Root Hub 10.0.18362.1 
Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D 9.3.0.1030 
Intel(R) 82579LM Gigabit Network Connection 12.15.31.4 
Aquantia AQtion USB to 5GbE Adapter 1.8.0.0 
USB Root Hub (USB 3.0) 10.0.18362.836 
USB xHCI Compliant Host Controller 10.0.18362.900 
Generic PnP Monitor 10.0.18362.693 
Intel(R) HD Graphics 10.18.10.5161 
HighPoint RCM Device 1.6.13.0 
Disk drive 10.0.18362.1350
RocketRAID 2720 SAS Controller 1.6.13.0 
Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root... 10.1.1.45 
Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor DRAM Controller ... 10.1.1.45 
PCI Express Root Complex 10.0.18362.1533
Microsoft ACPI-Compliant System 10.0.18362.1533
ACPI x64-based PC 10.0.18362.1 
Charge Arbitration Driver 10.0.18362.1 
UMBus Root Bus Enumerator 10.0.18362.329 
Microsoft Kernel Debug Network Adapter 10.0.18362.1 
Microsoft Storage Spaces Controller 10.0.18362.1533
Microsoft Virtual Drive Enumerator 10.0.18362.1 
Composite Bus Enumerator 10.0.18362.329 
Microsoft Hyper-V Virtualization Infrastructure Driver 10.0.18362.1316
Microsoft Basic Display Driver 10.0.18362.329 
WPD FileSystem Volume Driver 10.0.18362.1316
Volume 10.0.18362.1 
WPD FileSystem Volume Driver 10.0.18362.1316
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume 10.0.18362.1 
Volume Manager 10.0.18362.1500

2:10.0,2:6.3...
2:10.0,2:6.3...
2:10.0,2:6.3...
2:10.0,2:6.3...
2:10.0,2:6.3...
2:10.0,2:6.3...

Reply | Quote

Did you “compare” the lists from both PC’s to see if there were any differences? Especially in the versions of the drivers.

The easiest way to do that is to “sort” the results from both PC’s and then open both text files side-by-side so any lines with different info will standout.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Q: “Did you “compare” the lists from both PC’s to see if there were any differences?”

A:  not yet.

I do recall that one or more of the installed add-in cards did come with UNsigned drivers, and I had to choose “install anyway” (or similar bypass) to get those drivers installed.

I honestly do not see how or why the Highpoint 2720SGL RAID controller driver would be the problem, mainly because Windows Update Assistant does tons of I/O to that RAID-0 array.

Also, the two PCs are not EXACTLY  identical:  one also has a Highpoint RocketRAID 620,  and there are different USB 3.0 add-in cards installed in each PC.

I could replace the 620 add-in card with a newer model that has 4 x SATA-III ports.

BUT, here we are, doing what I wanted to avoid:

LOTS OF TRIALS / LOTS OF ERRORS / NO END IN SIGHT  ;-(

 

 

Reply | Quote

I followed your directions, and there are differences in the 2 lists of drivers.

On the problem PC, there are the following “drivers” that are NOT installed on the “good PC” (“good” =  22H2 installed AOK):

I’ll list those differences with Comments based on my prior knowledge:

——————————————————————————————–

(1)   American Power Conversion USB UPS

(2)  APC UPS

The latter have been OK for years:  there is a USB 2.0 cable that allows APC’s PowerChute Personal software to manage the UPS.  So, no problems apparent with (1) or (2) above.

——————————————————————————————–

(3)  Charge Arbitration Driver

I have NO IDEA what that driver might be.

——————————————————————————————–

(4)  HighPoint RCM Device

This is one of the drivers that supports the second Highpoint add-in controller.  So, no problem apparent with (4) above.

——————————————————————————————–

(5)  IDE Channel

(6)  IDE Channel

These 2 are VERY suspicious, chiefly because there is no IDE / PATA socket on this motherboard (i.e. that would require an ATA-133 parallel IDE ribbon cable).

——————————————————————————————–

(7)  RocketRAID 620 SATA Controller

Again, this is normal.  See (4) above.

——————————————————————————————–

(8)  Standard Dual Channel PCI IDE Controller

Again, VERY suspicious, for the reason stated at (6) above.

——————————————————————————————–

(9)  VIA USB 2 Hub

(10)  VIA USB 3 Root Hub

(11)  VIA USB eXtensible Host Controller

(12)  VIA USB Mass Storage Device (0711)

(13)  VIA USB Mass Storage Device (0711)

The latter 5 entries appear AOK because there is a USB 3.0 add-in card installed and working fine:  it presently controls 2 x 2.5″ WEC SATA SSDs via USB 3.0 cables and integrated controllers.

——————————————————————————————–

(14)  WPD File System Volume Driver

(15)  WPD File System volume Driver

I am not familiar with the latter 2 x drivers:  clearly, they concern the “File System” but I have no more information about either.

——————————————————————————————–

THAT’S ALL the “drivers” that appear on the problem PC that do NOT also appear on the other “good” PC.

 

Reply | Quote

This bothers me a lot because there is no PATA socket on this motherboard:

“Standard Dual Channel PCI IDE Controller” strongly suggests the presence of a legacy IDE PATA controller with matching socket for a PATA ATA-133 parallel ribbon cable.

Those PATA ribbon cables came with MASTER and SLAVE connectors, which corresponded to a MASTER and SLAVE jumper on a PATA HDD.

Note also:  “ATA Channel 0” and “ATA Channel 1” which match perfectly the  MASTER and SLAVE connectors on such a PATA ribbon cable.

My BEST GUESS now:  somehow this OS was installed with drivers for old PATA / IDE HDDs but withOUT any PATA / IDE socket present anywhere on the motherboard.

Here’s the relevant portion of a Device Manager screen shot:

 

Reply | Quote

Well (deep subject), I did learn something new, but I don’t know if it will make any difference.

Device Manager continues to list an IDE device, even though there is no PATA socket anywhere on the motherboard;  and, the .pdf User Manual also confirms that this PC does not support any IDE / PATA storage devices e.g. old PATA HDD or ODD.

In Device Manager, I can now DISABLE that phantom IDE controller, but I cannot UNINSTALL it.

If I try to UNINSTALL it, it comes right back after a RESTART.

If I DISABLE IT, it remains DISABLED after a RESTART, but NOT “uninstalled”.

So, I tried to locate an “IDE” device in the motherboard BIOS setup e.g. under “integrated controllers” (or similar descriptor) BUT there is no place in any BIOS Menus for DISABLING any “IDE” controller.

Where Windows 10 version 1909 is detecting some sort of “IDE controller” remains a total mystery to me.

NEXT STEP I believe will be a pointed request for Tech Support at HP’s User Forum.  Those folks are very capable, from prior experience I’ve had there.

By comparison, every ASUS motherboard I have ever built up myself, has ALWAYS had a BIOS feature for ENABLING or DISABLING on-board devices like integrated LAN controllers, RS232 serial ports,  etc.

For example, one ASUS motherboard has 2 x integrated Gigabit LAN controllers: one PCIe and one PCI.  I ENABLE the PCIe one, and DISABLE the PCI one.  These settings have always worked smoothly with all of our ASUS motherboards.

I hesitate to try another Windows Update Assistant, to see if DISABLING that phantom IDE controller will make any difference.

Another TRIAL and another ERROR?  Place your bets, ladies and gentlemen!!

Reply | Quote

The issue may not be as simple as drivers being used on your 1909 PC that are not on the 22H2 PC but the actual versions of the drivers (even those that are “shared” between the 2 PC’s.)

BTW, you can discount any 10.0.#.# driver versions as those are all “Windows drivers” and would get successfully updated to 22H2 versions.

Also bear in mind, there are some significant OS “core” differences between 1903/1909 and 2004/22H2… which is why it’s not possible to upgrade 1903/1909 to 22H2 using a simple “enablement package” like the upgrades from 2004 > 20H2 > 21H1 > 21H2 > 22H2!)

So, just because a particular device using a 3rd party driver has been working fine on Win10 1909, does not mean it’ll also work on Win10 22H2 (i.e the Conexant audio driver that caused 1903/1909 to 2004 – 22H2 update failures for some users is a perfect example!)

I’d “suggest” you check each of the 3rd party drivers to see if a newer version is available and, if so, update them.

As for the IDE drivers, if you disable them, they “should” be ignored during the update process.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Thank you!

I did double-check the latest driver for the Highpoint 2720SGL RAID controller, and I have already installed the latest version.

I’ll remember to check the latest drivers for other third-party add-in cards i.e. a Highpoint RocketRAID 620, and a USB 3.0 adapter with Via controller.

I have “disabled” the phantom IDE driver, but I have not yet tried Windows Update Assistant again after making that change.

Another option that failed once already is to run “setup.exe” on a brand new OEM DVD of 21H2.  It may install AOK now that the phantom IDE driver is “disabled”.

This phantom IDE driver remains an unsolved mystery:  HP’s documentation very clearly says that this motherboard has no PATA/IDE socket and does not support any PATA/IDE devices.

Also, yesterday I thoroughly reviewed every menu option in the motherboard BIOS, and there is no option to DISABLE that phantom IDE controller.

The only place it is even mentioned is “SATA emulation” = AHCI or IDE .  My setting is AHCI for all 3 x SATA drives ( 2 x SSD + 1 x HDD).

My BEST GUESS, as of today, is a very subtle bug in the latest motherboard BIOS: for example, I have also DISABLED the 1 x PCI slot in that BIOS.  Such a bug may be associated somehow with that change e.g. I can try ENABLING it to see if that makes any difference.

Because I’ll never need that 1 x PCI expansion slot, I installed a slot exhaust fan in that expansion slot which helps to cool the 2727SGL.

There is also a “Logicool HID-compliant Cordless Mouse” driver that is showing up in DriverEasy.

I’ve searched everywhere in my home lab, but failed to find the matching USB “dongle” for that mouse.  Logitech still sells that cordless mouse, so I can buy a new one for about $20.

Many MANY thanks for the extra insights.

 

p.s.  I’ve posted a help request with HP’s workstation experts, and I’m awaiting their reply(s).

Reply | Quote

same failure again this morning:

Reply | Quote

The “phantom IDE driver” shows up in Device Manager as follows,

under “IDE ATA/ATAPI controllers”:

Standard Dual Channel PCI IDE Controller

Reply | Quote

SupremeLaW wrote:

Because I’ll never need that 1 x PCI expansion slot, I installed a slot exhaust fan in that expansion slot which helps to cool the 2727SGL.

Is the exhaust fan actually plugged into the PCI slot and getting powered via the PCI bus or is it simply mounted to the rear of the case using a “slot cover plate” and powered by a connector from the PSU?

If it’s using the PCI bus, that might be the source of your phantom IDE driver.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

THIS:

simply mounted to the rear of the case using a “slot cover plate” and  powered by a connector from the PSU

There is NOTHING (ZERO) installed in that legacy PCI slot.

That slot is right next to the one x16 expansion slot, which hosts the RAID controller.

The idea is to assist air flow and cooling near that RAID controller.

The only other exhaust fans are in the HP PSU and the standard exhaust fan mounted in the rear panel.

I’ve added a red rectangle to show where that slot fan is installed:

Reply | Quote

motherboard layout:  to locate the x16 expansion slot where the RAID controller is installed and working AOK

the legacy PCI slot is the bottom “white” socket, directly below the RAID controller, where the extra exhaust fan is installed and working AOK:

Reply | Quote

SupremeLaW wrote:

There is also a “Logicool HID-compliant Cordless Mouse” driver that is showing up in DriverEasy. I’ve searched everywhere in my home lab, but failed to find the matching USB “dongle” for that mouse. Logitech still sells that cordless mouse, so I can buy a new one for about $20.

The “current” driver version for the Logicool mouse is shown as 10.0.18362.1 which means it’s using the Windows provided driver and isn’t whatever driver is causing your problem!

1 user thanked author for this post.

SupremeLaW

Reply | Quote

time permitting, I’ll remember to purchase a new Logitech cordless mouse, which should allow me to test it, and then UNINSTALL it completely.

I have no current need for a cordless mouse, chiefly because this workstation is hard-wired to a 4-port KVM switch which is shared with 3 other workstations.

One of those 3 other workstations is an HP Z240, which did update AOK to 22H2.

However, the Z240 is newer and I have NOT re-installed all third-party software on that PC (requires too much time).  It has a fast Intel Core i7-7700 + NVMe M.2 SSD hosting C: .

 

Reply | Quote

SupremeLaW wrote:

is there a way to confirm that VTx is enabled withOUT accessing the motherboard BIOS?

Search knows everything:

https://duckduckgo.com/?t=ffab&q=is+there+a+way+to+confirm+that+VTx+is+enabled+withOUT+accessing+the+motherboard+BIOS%3F&ia=web

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Y’all are being so very kind and patient with my latest dilemma here.

MUCH APPRECIATED!!

Reply | Quote

THE BAD NEWS:

Apparently 0xc1900101 is the most reported Windows 10 & 11 update error on Microsoft’s Feedback Hub

https://www.youtube.com/watch?v=fbYWA5Hb6Z0

Reply | Quote

Hadn’t remembered this one since it’s been so long ago when I updated from 1909 to 21H1 but…

If you system is using a Conexant audio driver (version 7.231.3.0 or older), it won’t update beyond 1909 unless you either update the driver to a newer version or uninstall it using device manager (choosing the option to “remove drivers“) and then immediately run the update without rebooting first.

If you system isn’t using a Conexant driver, you could try running Microsoft’s SetupDiag program to see if it “might” provide more info about exactly which driver is causing your problem.

Some online users have indicated they weren’t able to jump “directly” from 1909 to 22H2 but were able to go from 1909 to 2004 to 22H2 so another option would be to go to the UUPdump site and download the aria2 script files to create an ISO of the Feature update to Windows 10, version 2004 (19041.1415) and see if that’ll upgrade your 1909 to 2004?

If that works, then try to update to 22H2 again.

BTW, Microsoft force updated existing Win10 1903/1909 users to Win10 2004 way back in Jun – Nov 2020! Since that hasn’t happened to your Win10 1909 system, it’s unlikely their new forced updated to 22H2 starting in Jun 2023 will affect it.

Of course we are talking about Microsoft so, anything’s possible (although if you can’t get it to update because of an “incompatible” driver, they won’t be able to either… unless they uninstall, disable or update the problem driver.)

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Yes, I have already tried SetupDiag, and there was no clue about any faulty driver (see attached).

SetupDiagResults-2

Device Manager reports no faulty drivers.  And, I have enabled “Show hidden devices”.

DriverEasy reported 1 unplugged cordless mouse, and an Intel Watchdog Timer Driver that was outdated.  But, neither devices show up anywhere in Device Manager (see attached).

Also, DriverEasy freeware does not “install” without paying their license fee, so I can’t try that either.

If I could “install” these 2 drivers, I might be able to “uninstall” both devices.

I purchased this HP workstation several years ago, and it was already REFURBISHED.

So, I suspect that the OS was pre-installed by the seller — a Microsoft Authorized Refurbisher — using a cordless mouse, and that driver is still lurking around somewhere in the existing C: system partition.

I enabled WinUpdateStop, because of all the published complaints about Windows Update.  That was a wise decision, in retrospect, because it rendered this HP workstation VERY stable over the course of many years.

After downloading drivers from its website, DriverEasy does save those files in a sub-folder on C: .

The cordless mouse driver provided by DriverEasy is stored here:

Directory of C:\Users\supre\AppData\Roaming\Easeware\DriverEasy\drivers\l5hddr3d.ghz

06/02/2022 10:12 PM <DIR> .
06/02/2022 10:12 PM <DIR> ..
06/02/2022 10:11 PM 53,767 jfmouhid.cat
06/02/2022 10:12 PM 18,357 jfmouhid.inf
06/02/2022 10:11 PM 63,552 lhidfilt.sys
06/02/2022 10:12 PM 1,980,992 lkmdfcoinst.dll
06/02/2022 10:11 PM 54,336 lmoufilt.sys
06/02/2022 10:12 PM 113,216 lmoufiltcoinst.dll

The Intel Watchdog Timer Driver is stored here:

Directory of C:\Users\supre\AppData\Roaming\Easeware\DriverEasy\drivers\e0ighwgs.hcc

04/19/2022 10:54 AM <DIR> .
04/19/2022 10:54 AM <DIR> ..
04/19/2022 10:54 AM <DIR> x64
04/19/2022 10:54 AM 10,594 iccwdt.cat
04/19/2022 10:54 AM 2,163 iccwdt.inf
04/19/2022 10:54 AM 35,592 iccwdt.sys

However, a search everywhere in C: does not find any other instances of those .sys files e.g.:

in elevated Command Prompt mode:

C:

cd \

attrib iccwdt.sys /s

attrib lhidfilt.sys /s

attrib lmoufilt.sys /s

only finds the files listed above, but no such files are found in C:\Windows\system32\drivers where installed drivers are normally stored.

(I use ATTRIB in this mode because it’s so very fast, from past experience.)

Lastly, at YouTube I found a short video of a IT tech who fixed this chronic problem simply by switching the SATA cable to a different SATA port on his Dell motherboard.

When I read the HP documentation for this HP Compaq Pro 6300 MT, there is mention of an “IDE” controller, but there are no PATA sockets on the motherboard.

So, I’m guessing here that HP’s chipset driver set for this motherboard still has an “IDE” device buried deep somewhere, and Windows Update Assistant finds it to be “incompatible”.

Reply | Quote

OOPS (again).  SetupDiag results are being blocked by this Forum’s security policy.

2 halves are posted up above in this Topic.

The relevant subset is repeated here:

Error: SetupDiag reports rollback failure found.
Last Phase = Finalize
Last Operation = Remove System Restore checkpoints
Error = 0xC1900101-0x20017
LogEntry: 

Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.

Reply | Quote

You may want to read this:
https://learn.microsoft.com/en-us/windows-hardware/drivers/install/using-device-manager-to-uninstall-devices-and-driver-packages

If you decide to try this approach, create an image backup firat.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Many thanks.

FYI: I’ve posted a Help Request at the HP Expert Center.

This driver theory may be a dead end (as in barking up the wrong tree).

I do remain “dogged” about this issue (same as “grim persistence” 🙂

I’ll report back with any suggestions I get from the HP Expert Center.

Reply | Quote

My help request to the HP Expert Center:

[BEGIN QUOTE]

Microsoft Windows 10 (64-bit)

We are trying to upgrade Windows 10 version 1909 to Windows 10 22H2 on our HP Compaq Pro 6300 MT.

No matter what we have tried so far, we continue to see error code “0xC1900101-0x20017” after a total ROLL-BACK.

Delving deeper, we discovered that a phantom “IDE” device is showing up in Device Manager, EVEN THOUGH this motherboard has no on-board PATA sockets (for Parallel ATA HDDs or ODDs).

A search of the Internet for that error code finds results that suspect a device driver as the reason for the ROLL-BACK and fatal error code.  But, our efforts to locate such a driver in the update logs turned up empty.

We have also tried to locate an “IDE” device in the motherboard BIOS, but there is no such device or controller listed there.

We have set SATA Emulation to AHCI, NOT IDE.

The motherboard documentation also confirms that this PC does not support ANY IDE devices (none).

This is a tough one, and we’re a bit tired of so many trials-and-errors, with no success to date.

Microsoft now says they intend to FORCE 22H2 on all Windows 10 users (?).

[END QUOTE]

Reply | Quote

So, I honestly guess that an “IDE driver” is loaded automatically, in case the User chooses the “IDE” SATA emulation option in the motherboard BIOS.

And, this “IDE driver” must be loaded EVEN IF the User chooses “AHCI” SATA emulation instead of “IDE” SATA emulation.

Just another educated guess here.

Reply | Quote

REPLY today from HP workstation expert:

[BEGIN QUOTE]

Subject: Re: “0xC1900101-0x20017” during Windows Update Assistant

software related issues can be hard to pin down and since you are using a old release of win 10 currently and having problems with a in place update, consider doing a clean install, this method can save you much time and frustration   I personally have a 6300 pro (SFF model) which uses the exact same motherboard,.. and windows 10 22H2 64bit installs without any issues and includes all necessary drivers for this models hardware short of some add in discrete video cards and printer drivers   i would simply backup your existing data, download the win 10 installer of your choice (usb key or Iso) install the OS and be done with it

[END QUOTE]

Reply | Quote

my REPLY to the HP workstation expert:

[BEGIN QUOTE]

I do appreciate your consideration for my time and frustration.

By “clean install” I infer that I will need to re-install ALL third-party software, a licensed copy of MS WORD, custom FTP software for website maintenance, and a collection of other utilities.

That requirement does NOT save me much time and frustration.

I can save much time and frustration by simply GIVING UP!!

I was quite unhappy reading at msn.com that MS now intends to FORCE 22H2 on all Windows 10 PCs.

I will NOT allow MS to FORCE anything on me.  If nothing else, the tone of that intent is OFFENSIVE.

Because it is the MS OS update that is issuing the fatal error message,

at a very MINIMUM MS system software should provide a lot more information about any incompatible driver(s).

I have done systems programming many years ago: 

that is the minimum any system administrator has every reason to expect.

FYI:  long Topic now at askwoody [dot] com :

[END QUOTE]

Reply | Quote

I agree with HP about wiping the hard drive and installing a fresh copy of Windows as something is clearly amiss with the existing Windows installation with no end in site of possibly getting it fixed after six days of troubleshooting.

Sometimes you just have to take the hard road and nuke it from orbit (it’s the only way to be sure) and start over from scratch. Chances are it works and you will have a functioning system again and know that it’s a solid foundation to build on and re-install all needed software. Worse case if it doesn’t work, restore your drive image and continue troubleshooting.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

I fully appreciate why you are advising that probable solution, and I am sincerely grateful and understanding why it may have potential, and could succeed assuming I am willing to re-install ALL third-party software and similar system management utilities.

Nevertheless, the evidence already documented in this Topic above includes all the following:

(1)  updating 2 identical motherboards, one succeeds the first time, and one fails multiple times during normal Windows Update, running Windows Update Assistant, and running “setup.exe” on an OEM DVD with Windows 10 21H2 purchased from Newegg last August

(2) the majority of professional opinions point to some device driver that is not identified any further in any of those opinions, however;  at best those opinions recommend disconnecting ALL peripherals and resorting to more trials-and-errors

(3) the Windows Update code does not presently report any specific device driver(s) that might be causing the error and ROLL-BACK, whether “signed” or “unsigned”: the point at which that error is detected would be the best place to report much more diagnostic information and to store that information in a proper update log

(4)  a search of the Windows Update logs does not find any specific device driver(s) that are causing the error

(5)  a list of “signed” drivers does reveal a few drivers on the failing PC that are not in the other successful PC’s list of “signed” drivers

(6)  a rather obvious stance of (5) is a “Standard Dual Channel PCI IDE Controller”

(7)  however, the failing PC’s motherboard has no IDE/PATA sockets anywhere, and the Device Manager on the successful PC does not show that PCI IDE Controller

(8)  HP’s motherboard documentation also confirms (7) above (no IDE/PATA support)

(9)  the failing PC has a newer motherboard BIOS, downloaded from HP’s website, and that newer BIOS is the latest version, successfully installed in the failing PC several months back

(10)  it is very UNLIKELY that the driver for the Highpoint RocketRAID 2720SGL RAID controller is the culprit, because both PCs host the C: system partition on that same add-in card, and the long Windows Update process must perform HEAVY I/O with that add-in controller

(11)  further research of relevant documentation on the Internet confirms that the error code in question has been occurring on many PCs worldwide:  reportedly it is the single most frequent error code being reported to Microsoft during the past 2 years

(12)  if verifiable, the reports summarized at (11) above would strongly suggest that Microsoft escalate that error code by dedicating capable in-house engineering expertise to identify the source(s) of that error and to publish one or more effective solutions

(13)  specifically, any Microsoft software that issues that same error code can and should be modified to add more executing code that attempts to identify any suspicious device driver(s) and/or to report any other diagnostic information that can help Windows Update to complete successfully withOUT a total ROLL-BACK

(14) adding even more urgency to all the above is a recent report published at msn.com that Microsoft now intends to FORCE Windows Updates to version 22H2

(15)  I am going to the trouble of documenting all of the above, because the level of details above may come to the attention of experts at Microsoft who are capable and in a position to escalate this frequently occurring error code, given the large number of Microsoft customers who are experiencing the same or similar faults.

Reply | Quote

I advise an attempt with upgrading step by step, first using the setup.exe in the mounted ISO for Windows 10 2004. (2020 April)  If it does not fails with the same error code, and successfully installs 2004 further upgrades or “enablement packages” could work.  Above is a link to how to get 2004.

The other thing I might try if it still fails is disconnecting all hard drives (and optical drives) other than the boot drive during upgrade process.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

SupremeLaW wrote:

(9) the failing PC has a newer motherboard BIOS, downloaded from HP’s website, and that newer BIOS is the latest version, successfully installed in the failing PC several months back

If I’m understanding your above statement correctly, the BIOS on the successfully updated PC is an older version than the failing PC?

That would mean the PC with the “older” BIOS doesn’t show an IDE controller while the PC with the “newer” BIOS does; even though there’s no IDE device installed in it that would require such a driver!

I know it’s not normal procedure to do this but, I’ve seen a lot of online posts over the years where an “updated” BIOS caused users various problems (including not being able to update their OS) and the fix was to download/install an older BIOS version for their motherboard (i.e. “downgrade” the BIOS.)

Since the older version worked just fine for upgrading the other PC, I’d suggest you download/install it on the failing PC and see if that lets you upgrade it… or at the very least gets rid of the phantom IDE device.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Re: “If I’m understanding your above statement correctly, the BIOS on the successfully updated PC is an older version than the failing PC?”

CORRECT!

 

Re: “That would mean the PC with the “older” BIOS doesn’t show an IDE controller while the PC with the “newer” BIOS does; even though there’s no IDE device installed in it that would require such a driver!”

CORRECT!

 

There are NO (zero) IDE / PATA sockets anywhere on the Paul27 motherboard, and that fact is CONFIRMED by HP’s technical documentation.

I ran CPU-Z to confirm your theory:

Paul27 has BIOS v3.08 = failing updates

Paul26 has BIOS v2.83= successful updates

Re:  “Since the older version worked just fine for upgrading the other PC, I’d suggest you download/install it on the failing PC and see if that lets you upgrade it… or at the very least gets rid of the phantom IDE device.”

That may be worthy of a try:  I should contact HP first because I seem to recall that reverting to an older motherboard BIOS is BLOCKED by HP’s BIOS update sequence.

So, I’ll need to ask them first, before trying that.

And, HP’s Support Assistant software may be able to help with that decision.

Also, there may be a way to SAVE the BIOS v.2.83 file and simply copy that over our LAN to Paul27.

Reply | Quote

History.txt file for latest motherboard BIOS says:

[BEGIN QUOTE]

Version 3.08

*** ALERT *** ALERT *** ALERT ***

If upgrading from a v02.xx to this version, v03.xx, the user MUST FIRST FLASH TO v02.99.

If not, upgrading to v03.xx will be rejected.

– Provides latest Intel Microcode versions 0x21 for Ivy Bridge processors and 0x2F for Sandy Bridge processors.

NOTE: Due to security changes, after loading this BIOS, older versions cannot be installed.

[END QUOTE]

Reply | Quote

SupremeLaW wrote:

NOTE: Due to security changes, after loading this BIOS, older versions cannot be installed.

So they “deliberately” removed a users ability to downgrade their BIOS if the newer version causes problems!

Typical HP behavior!

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Re:  “So they ‘deliberately’ removed a users ability to downgrade their BIOS if the newer version causes problems!”

CORRECT!

Reply | Quote

And, MANY THANKS for following my train of thought.

Here’s a scenario that may explain why the latest BIOS is defective:

phantom driver is clearly related to the legacy PCI slot (white expansion socket) because of this obvious reference to “PCI IDE”:

“Standard Dual Channel PCI IDE Controller”

as such, that says to me that HP’s chipset hosted IDE controllers on the PCI bus, which was fast enough for spinning platters:  ATA-133 = 133 MB/second MAX HEADROOM on that bus:

32 bits @ 33 MHz  ~= 1,056 Mb/second ~= 1GbE NIC / 8 bits per byte ~= 132MB/sec

likewise, Gigabit LAN controllers operate at the same speed, so HP needed to continue supporting that white PCI expansion slot for all such add-in cards

HECK, maybe I should pull the PCI slot fan and try a legacy 1GbE NIC in the white PCI expansion slot!!

back in year 2012, those legacy PCI slots were much more popular than they are now, and similarly PATA HDDS were true of a much larger installed base of PCs worldwide

my theory is that turnover inside HP resulted in less experienced programmers assigned to updating the BIOS to its 2019 version

there was probably something like an isolated need to support a PCI-to-IDE add-in card (AIC) that HP agreed to support with updates to the motherboard BIOS

thus, insert AIC in PCI slot; connect IDE/PATA HDDs to AIC; RESTART; load driver for AIC;  format HDDs;  etc.

-AND/OR-

which is more probable:  continue supporting Gigabit NICs in the latest BIOS

 

Reply | Quote

Speaking of 2012, I can’t believe how TIME FLIES!

What a difference, after the IT industry realized the benefits made possible by “syncing” chipsets with storage devices  🙂

Now we have idle CPU cores talking DIRECTLY to M.2 sockets.

 

Reply | Quote

SupremeLaW wrote:

HECK, maybe I should pull the PCI slot fan and try a legacy 1GbE NIC in the white PCI expansion slot!!

Insert the part that isn’t there…

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

SupremeLaW

Reply | Quote

RE:  “Insert the part that isn’t there…”

CORRECT!

I’m almost willing to bet that HP offered a proprietary PCI-to-IDE/PATA add-in card for something like tens of thousands of HP customers who still needed to install spinning platter HDDs with 40-pin parallel ribbon connectors e.g. with the ol’ MASTER and SLAVER jumper.

Reply | Quote

Here’s the sort of PCI add-in card that requires an IDE/PATA driver:

1 Port eSATA + 1 Port SATA PCI SATA Controller Card w/ LP Bracket

Add an internal SATA port and an external SATA (eSATA) port to your desktop computer through a PCI expansion slot

https://www.startech.com/en-us/cards-adapters/pciesata2i

I’m making an educated guess here that many HP customers, when this PC was new, still had spinning platter HDDs they needed to install in this PC.

As such, an add-in card was necessary because there are no PATA sockets anywhere on this motherboard.

Reply | Quote

… only difference being a PATA socket on the add-in card INSTEAD OF a standard SATA socket.

Reply | Quote

In the motherboard BIOS,

menu option Security > Slot Security , PCI is now ENABLED.

In Device Manager, under IDE ATA/ATAPI controllers,

“Standard Dual Channel PCI IDE Controller” is now ENABLED.

Windows Update Assistant result:  SAME ERROR MESSAGE as above:

Reply | Quote

Make a full image backup to external disk. Check it by mounting the backup and view some of the data you have added / changed – e.g. desktop icons.
Boot from the Windows installation media.
Install Windows from scratch.
Try to update to 22H2.

If this works you know the issue is in your current config and you then have the choice of continuing your chase or re-installing / tweaking all your stuff.

cheers, Paul

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Yes, we considered that general approach earlier in this Topic i.e.

I can purchase a new 2TB SSD, insert it into one of the Icy Dock bays accessible at the front panel, and run “Migrate OS” in Partition Wizard.

At that point, I SHOULD BE able to change the boot drive in the motherboard BIOS and boot directly from that new JBOD SSD.

Then, I have the option to disconnect the Highpoint RAID  controller and 2 other add-in cards, and then try Windows Update on that brand new JBOD SSD.

But, frankly, “Migrate OS” is probably going to drag “phantom driver” along with everything else, using that approach.

Another option arose last evening:  used versions of this PC are very cheap at eBay now, and a few of them might still have older BIOS versions.  I should be able to transfer all peripherals and add-in cards to the same motherboard but with an older BIOS version.

Reply | Quote

in elevated Command Prompt, I did:

C:

cd \

attrib pciide.sys /s >E:\log.txt

Here’s log.txt :

C:\Windows\SoftwareDistribution\Download\24e8a2276eae23c74ec6e3c4b93f9a94\amd64_Microsoft-Windows-Client-Desktop-Required-Package~~amd64~~10.0.19041.1\amd64_dual_mshdc.inf_31bf3856ad364e35_10.0.19041.1_none_d168bf476edd273a\pciide.sys
C:\Windows\System32\drivers\pciide.sys
C:\Windows\System32\DriverStore\FileRepository\mshdc.inf_amd64_3ed75b903980b6f2\pciide.sys
C:\Windows\WinSxS\amd64_dual_mshdc.inf_31bf3856ad364e35_10.0.18362.1533_none_28fdaea632713b84\f\pciide.sys
C:\Windows\WinSxS\amd64_dual_mshdc.inf_31bf3856ad364e35_10.0.18362.1533_none_28fdaea632713b84\r\pciide.sys
C:\Windows\WinSxS\amd64_dual_mshdc.inf_31bf3856ad364e35_10.0.18362.1533_none_28fdaea632713b84\pciide.sys

Reply | Quote

You have several alternatives now open to you. What is your next step?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Q:  “What is your next step?”

Because this PC continues to operate smoothly and reliably with Windows 10 version 1909, I am very reluctant to tear it down merely to get Windows Update working without that fatal error code and a total ROLL-BACK.

I still have a brand new OEM DVD of Windows 10 Pro 21H2.

And, at eBay these used PCs are very cheap now.

Yesterday, I wrote to one of the sellers to ask if s/he could reply with the motherboard BIOS version.  No answer yet from that eBay seller.

If that version is older than v03.08, I could try doing a fresh install of 21H2 from my OEM DVD.  That option is attractive because I would not need to begin tearing down this fully functional PC.

Also, an expert at HP’s Support Forum confirmed that 22H2 installed AOK on his identical HP Compaq Pro 6300 MT.  I’ve replied this morning to ask if he could disclose his motherboard’s BIOS version.  No answer yet from him.

Also, Susan Bradley has jumped in, to ask if I could send her the update logs stored in the “Panther” sub-folder, chiefly setuperr.log .

But, when I searched for that one filename, Windows found several occurrences of the same filename in the C: system partition.  In elevated Command Prompt:

C:

cd \

attrib setuperr.log /s >E:\loglist.txt

I’ve searched a few of those .log files for the error codes in question, but that search turned up empty.

Those .log files reportedly contain pointers to problem drivers that may have caused the ROLL-BACK.

Here’s the text in loglist.txt as written by the ATTRIB command above:

A I C:\$SysReset\Logs\setuperr.log
A I C:\$WINDOWS.~BT\Sources\Panther\setuperr.log
A I C:\$WINDOWS.~BT\Sources\Rollback\setuperr.log
A I C:\$Windows.~WS\Sources\Panther\setuperr.log
A I C:\Windows\Logs\DPX\setuperr.log
A I C:\Windows\Logs\SetupSnapshotCleanupTask\setuperr.log
A I C:\Windows\Logs\WinREAgent\setuperr.log
A I C:\Windows\Panther\NewOs\Panther\setuperr.log
A I C:\Windows\Panther\UnattendGC\setuperr.log
A I C:\Windows\System32\LogFiles\setupcln\setuperr.log
A I C:\Windows\setuperr.log

EDIT:  the latter list got corrupted here ;  above are correct contents of loglist.txt .

The BIG UNKNOWN is the real possibility that further technical problems might arise if I decide to re-install all third-party software e.g. licensed copies of MS Word and Partition Wizard (to name just 2 such software packages now installed and working AOK).

And, at the end of the day, no one has shown me any marginal, and irresistible, benefit I can expect to obtain from upgrading to 22H2.

I am already blocking Windows Updates with the WinUpdateStop third-party software, which has worked very well for me:  it’s the reason why I’m still at version 1909 and that software has clearly made it possible for me to avoid any of the myriad problems with MS Windows Update, as superbly documented by Susan Bradley.

Next step:  wait for answers to my requests for motherboard BIOS versions from other users of the same PC.

Reply | Quote

Some of the setuperr.log files were empty (0 bytes).

Here’s a list of the setuperr.log files that were NOT empty:

Directory of C:\$SysReset\Logs

05/24/2023 10:55 AM 527 setuperr.log
1 File(s) 527 bytes

Directory of C:\$WINDOWS.~BT\Sources\Panther

05/26/2023 01:12 PM 33,341 setuperr.log
1 File(s) 33,341 bytes

Directory of C:\$WINDOWS.~BT\Sources\Rollback

05/26/2023 01:19 PM 328 setuperr.log
1 File(s) 328 bytes

Directory of C:\$Windows.~WS\Sources\Panther

05/26/2023 12:57 PM 615 setuperr.log
1 File(s) 615 bytes

Directory of C:\Windows\Panther\NewOs\Panther

05/26/2023 07:56 AM 615 setuperr.log
1 File(s) 615 bytes

Directory of C:\Windows\System32\LogFiles\setupcln

05/26/2023 05:16 PM 2,122,017 setuperr.log
1 File(s) 2,122,017 bytes

Reply | Quote

in the folder:

C:\Windows\Panther\NewOs\Panther

here are the entire contents of setuperr.log :

2023-05-26 07:52:44, Error MOUPG CInstallUI::GetDefaultLanguage(2027): Result = 0x80070002[gle=0x00000002]
2023-05-26 07:56:21, Error MOUPG CSetupManager::GetDUSetupResults(6511): Result = 0x80070490
2023-05-26 07:56:22, Error MOUPG CDlpTask::Cancel(982): Result = 0xC1800104
2023-05-26 07:56:22, Error MOUPG CDlpTask::Cancel(982): Result = 0xC1800104
2023-05-26 07:56:22, Error MOUPG CDlpTask::Cancel(982): Result = 0xC1800104
2023-05-26 07:56:22, Error MOUPG CDlpTask::Cancel(982): Result = 0xC1800104

Reply | Quote

in the folder

C:\$WINDOWS.~BT\Sources\Rollback

here are the entire contents of setuperr.log :

2023-05-26 13:17:53, Error SP CSetupPlatformOSSwitchCheckpoint::Rollback: Failed to read the rollback GUID from file: C:\$WINDOWS.~BT\Sources\Rollback\rollbackinfo.ini. Error: 0x00000002[gle=0x00000002]
2023-05-26 13:19:15, Error SP Failed to merge telemetry file: . hr = 0X80070057

Reply | Quote

in the folder:

C:\$SysReset\Logs

here are the entire contents of setuperr.log :

2023-05-24 10:55:08, Error 0x80070002 in PushButtonReset::RegKey::HasValue (base\reset\util\src\registry.cpp:187): Failed to load subkey at [Microsoft\Windows\Signature][gle=0x00000002]
2023-05-24 10:55:08, Error 0x80070002 in PbrGetRestoreToBaselineVal (base\reset\engine\scenario\src\sensetargetos.cpp:63): Does not find registry key of PushButtonReset[gle=0x00000002]
2023-05-24 10:55:08, Error Factory: No recovery image registered[gle=0x000000ea]

Reply | Quote

filename setupact.log also keeps showing up

here’s a list of those full pathnames and their sizes from DIR command (96.7 Megabytes total):

A I C:\$SysReset\Logs\setupact.log
A I C:\$WINDOWS.~BT\Sources\Panther\setupact.log
A I C:\$WINDOWS.~BT\Sources\Rollback\setupact.log
A I C:\$Windows.~WS\Sources\Panther\setupact.log
A I C:\Windows\Logs\DPX\setupact.log
A I C:\Windows\Logs\SetupSnapshotCleanupTask\setupact.log
A I C:\Windows\Logs\WinREAgent\setupact.log
A I C:\Windows\Panther\NewOs\Panther\setupact.log
A I C:\Windows\Panther\UnattendGC\setupact.log
A I C:\Windows\System32\LogFiles\setupcln\setupact.log
A I C:\Windows\setupact.log


Directory of C:\$SysReset\Logs

05/24/2023 10:55 AM 15,052 setupact.log
1 File(s) 15,052 bytes

Directory of C:\$WINDOWS.~BT\Sources\Panther

05/26/2023 01:14 PM 76,580,372 setupact.log
1 File(s) 76,580,372 bytes

Directory of C:\$WINDOWS.~BT\Sources\Rollback

05/26/2023 01:19 PM 72,776 setupact.log
1 File(s) 72,776 bytes

Directory of C:\$Windows.~WS\Sources\Panther

05/26/2023 12:57 PM 89,056 setupact.log
1 File(s) 89,056 bytes

Directory of C:\Windows

05/26/2023 01:14 PM 12,346 setupact.log
1 File(s) 12,346 bytes

Directory of C:\Windows\Logs\DPX

05/23/2023 10:47 AM 2,173,436 setupact.log
1 File(s) 2,173,436 bytes

Directory of C:\Windows\Logs\SetupSnapshotCleanupTask

05/25/2023 04:39 PM 643 setupact.log
1 File(s) 643 bytes

Directory of C:\Windows\Logs\WinREAgent

05/21/2023 01:57 PM 104,347 setupact.log
1 File(s) 104,347 bytes

Directory of C:\Windows\Panther\NewOs\Panther

05/26/2023 07:56 AM 87,989 setupact.log
1 File(s) 87,989 bytes

Directory of C:\Windows\Panther\UnattendGC

05/27/2023 06:37 AM 7,110 setupact.log
1 File(s) 7,110 bytes

Directory of C:\Windows\System32\LogFiles\setupcln

05/26/2023 05:16 PM 17,627,887 setupact.log
1 File(s) 17,627,887 bytes

Total Files Listed:
11 File(s) 96,771,014 bytes
0 Dir(s) 29,703,299,072 bytes free

Reply | Quote

Windows Upgrade Log Files

“Several log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems.”

https://learn.microsoft.com/en-us/windows/deployment/upgrade/log-files

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

SupremeLaW

Reply | Quote

The error code I’m getting consistently is:  0xC1900101-0x20017

I have already searched several of these log files for 1900101 , per the instructions.

But, starting at the bottom and searching UP with NOTEPAD, no such 1900101 was found.

Reply | Quote

If this were my computer, I’d do a clean install.  I think there’s been some setting done along the way that this install doesn’t like.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Thank you very much, Susan:  I appreciate the patience you and others here have shown in my hour (now full week) of need.

I know you don’t like those third-party driver updaters, and for good reasons.

Nevertheless, moments ago I tried the freeware version of AVG Driver Updater, and without requiring payment it did successfully locate 2 x device drivers that needed updating.

I am already an AVG customer:  I’ve purchased and downloaded their AVG Internet Security and AVG AntiVirus software packages with much success (not perfect, but good enough).

Good News and Bad News:

Good:  Highpoint RCM Device driver was successfully updated to the newest version 1.6.13.0 using Device Manager to do so.

BAD:  VIA USB 3 Root Hub driver is currently version 6.1.7600.4903;  the newest version according to AVG Driver Updater is version 6.1.7600.5601, but Device Manager did NOT succeed in updating that driver to that newest version.

The latter VIA controller is on a x1 PCIe USB 3.0 add-in card currently hosting 2 x 2.5″ SSDs connected to 2 x USB 3.0 cables and in-line controllers.  I just tested both of those 2 x SSDs, and they continue to function properly, after a routine RESTART.

I also double-checked the status of the Highpoint RocketRAID 620 after RESTART, using their GUI to manage RAID arrays.  Both drives wired to that 620 continue to function properly.

I’m going to search the VIA website later today, to see if they have a driver update package with which I can download and try to install VIA USB 3 Root Hub driver version 6.1.7600.5601 .

That is all, for now.

MANY THANKS, again, for everyone’s participation here.

 

Reply | Quote

What we are all saying is “stop trying to fix the current Windows install and install a fresh one”.
This is the only way to work out if it’s a setting/corruption or a standard driver problem.

cheers, Paul

2 users thanked author for this post.

Just another Forum Poster, SupremeLaW

Reply | Quote

Re: “This is the only way to work out if it’s a setting/corruption or a standard driver problem.”

I do appreciate how you reached that conclusion.

My answer below is a bit long-winded; just stop reading if you’re not interested.

However, there still remains the problem of the “phantom driver” (as I have called it):

I can buy a new SSD and start from scratch with a fresh install of Windows 10, but that sequence is STILL going to detect “phantom driver” and add that driver to the Device Manager list.

Under “IDE ATA/ATAPI controllers” in Device Manager, there is this phantom driver:

“Standard Dual Channel PCI IDE Controller”

If I UNINSTALL it, it returns after a RESTART.

If I DISABLE it, that makes no difference for Windows Update Assistant etc. because I get the same error code and ROLL-BACK whether that phantom driver is ENABLED or DISABLED.

An HP User Support specialist confirmed that he has the exact same motherboard, and 22H2 updated AOK.  I also have a SFF version with the exact same motherboard, and 22H2 updated AOK for me too.

The motherboard BIOS version in the latter SFF is older.

The motherboard BIOS version in the problem PC is newer.

However, HP’s documentation says that the latter (newer) BIOS can NOT be replaced with any older versions.

So, I can’t try to ROLL-BACK the motherboard BIOS to a version that does not list “phantom driver” in Device Manager.

Yesterday, I tried AVG Driver Updater, and it did find 2 drivers that needed updating.

I found and installed one of those 2 drivers, but the other resulted in a yellow bang sign “!” after I tried to install it.  The latter controller is a ViaLabs model DW-VL805-4 on a x1 PCIe USB 3.0 add-in card (adds 2 x USB 3.0 Type-A ports at rear I/O panel).

No matter how hard I try to locate the latest Windows 10 driver for the latter controller, the ONLY one with matching driver filename causes that yellow bang sign”!”.

Here is what I now suspect is the explanation for “phantom driver”:

The age of this problem PC tells me that Users who purchased it brand new, had a need to connect IDE / PATA HDDs in the 3.5″ internal drive bays BUT there are no IDE / PATA sockets anywhere on that motherboard.

The solution back then was to install a PCI add-in card with one or two PATA 40-pin sockets.

With one such socket, a standard 40-pin ribbon cable would have MASTER and SLAVE connectors at the other end, and the HDDs needed to have jumpers installed to match MASTER and SLAVE.

With two such sockets, one would operate as MASTER and the other would operate as SLAVE.  I posted a photo of one such AIC above (“far” above 🙂

Another option was called CABLE SELECT, which also required jumper settings.

My theory about “phantom driver” is that a programming error occurred with the latest motherboard BIOS, and it continues to detect a “Standard Dual Channel PCI IDE Controller” when no such Controller is integrated onto this motherboard, and no such PCI add-in card is now installed that would trigger the installation of a device driver for a “Standard Dual Channel PCI IDE Controller”.

The correct test of the latter theory requires another identical motherboard with an older BIOS version, NOT the latest BIOS version.

Reply | Quote

@supremelaw, you’re missing the whole point of attempting a clean install of 22H2.

At this point you do not really know what’s actually causing the update failures. You’ve assumed it’s an incompatible driver due to Microsoft’s explanation of the specific error code you keep getting and have now obsessing over the “phantom IDE driver” and how to get rid of it thinking that’s your problem.

However, if you go back and look at the driver info you got using my powershell suggestion (your post #2561825), you”ll see it’s listed as Standard Dual Channel PCI IDE Controller 10.0.18362.1533 which means it’s using a “Windows supplied driver” and thus would not be causing that error (i.e. Windows supplied drivers aren’t going to be incompatible between OS versions because they will be replaced with newer ones if needed!)

Also, that particular error seems to be extremely common and some of the various solutions that allowed users to successfully complete the update weren’t due to driver issues (i.e. incorrect registry settings, not enough disc space, incompatible BIOS, etc., etc.)

At this point, doing a clean install of 22H2 on the problem PC (after making a full image backup first of course so you can restore things to their current state) will quickly tell you if the problem is your current H/W or BIOS configuration (the update still fails) or if it’s something else (the update succeeds.)

Depending on the results, you can then proceed in a “much more informed fashion” to figure out exactly what you want to do:

• Keep trying to figure out what’s causing the failure and fix it so you can update that system.

• Do a clean install and then reinstall all the existing S/W.

• Keep that system “as is” until such time as you must replace it.

We’re simply trying to provide some guidance as how “we’d” proceed in this situation but… ultimately it is your system and your decision!

2 users thanked author for this post.

SupremeLaW, geekdom

Reply | Quote

Many thanks for the lengthy reply.

I wouldn’t agree that I am “obsessing”;  I have simply decided AGAINST a fresh install to a newly formatted SSD.

(I don’t happen to have a new SSD in spare parts at this very moment.)

You are free to disagree with my decision.

I’m not at all bothered by such a disagreement.  I believe disagreements can be healthy and productive.

As such, I have also decided AGAINST re-installing all third-party software and similar utilities.

Assuming a fresh OS install, and a re-install of ALL that additional software, all work perfectly, THEN Windows Update should install 22H2 with no further errors.

That long sequence (with no guarantees) brings me right back to where I am now.

In other words, using cost-benefit analysis, lots of cost (much additional time spent) divided by zero marginal benefit is the same as dividing by zero.

I don’t honestly understand all the dire warnings if I do NOT upgrade to 22H2.  If anyone is “obsessing” in this matter, it appears to be a few Prosumers who want me to believe the sky is falling, when it’s not — not on my head, anyway  🙂

Call me a heretic, if you must:  I DON’T MIND WHAT LABELS YOU PREFER.

On the contrary, WinUpdateStop has allowed this PC to work reliably and productively for many years.  It has helped me AVOID ENTIRELY all of the messy and unending problems that Susan has documented in such enormous details over a period spanning YEARS.

Case in point: didn’t a few recent Windows Updates completely DISABLE printers?

If I do decide to continue trouble-shooting, my curiosity alone recommends purchasing a very cheap, used, version of this same motherboard, as a means to confirm whether or not a prior motherboard BIOS version cures the problem that keeps repeating with the ROLL-BACK etc.

In particular, the BIOS documentation has the menu option “Device Security”:

“Allows you to set Device Available/Device Hidden (default is Device Available) for:”

What follows is a list of on-board devices e.g. “Network controller”, “Serial port”, “Parallel port” etc. i.e. all the integrated devices one normally expects to find on most motherboards.

BUT THERE IS NO “Standard Dual Channel PCI IDE Controller” in that list that can be set to “Device Hidden”.

Elsewhere in that BIOS documentation, under “Advanced > Onboard Devices”,  it also says:

“To hide a device from the operating system, see Security > Device Security.”

See above where I already followed that advice, only to confirm a “PCI IDE Controller” is MISSING from the list of Onboard Devices.

The Windows Plug-and-Play subsystem should NOT be loading a device driver for a device that is DISABLED in the motherboard BIOS.  This is how ALL of our ASUS motherboard BIOS subsystems function properly.

Reply | Quote

$75 + $25 expedited shipping:

HP COMPAQ PRO 6300 MT INTEL CORE I5-3570 3.40GHz 16GB NO HDD/CADDY/OS

https://www.ebay.com/itm/285288617053?mkevt=1&mkpid=2&emsid=e90001.m43.l3160&plmtId=700008&mesgId=3024&mkcid=8&ch=osgood&bu=44660518646&trkId=e1f1dcfc-00f7-4ddf-a434-6b0f99a2ddf4&cnvId=700003&recoId=285288617053&recoPos=1

 

Reply | Quote

What triggered this ENTIRE topic was the recommendation to update Windows 10 to version 22H2.

Don’t forget that MS has announced their intentions to FORCE updates to 22H2.

All of the problems that arose for me by following that recommendation would NOT have occurred, if I had NOT followed that recommendation and stayed with 1909.

Here’s the OUTSTANDING / UNANSWERED QUESTION:

How is MS going to FORCE my PC to upgrade to 22H2, if every single attempt to do so has failed with the same error code and total ROLL-BACK?

Perhaps someone among their most experienced engineers will answer that question.

I’m not holding my breath.

Reply | Quote

SupremeLaW wrote:

How is MS going to FORCE my PC to upgrade to 22H2, if every single attempt to do so has failed with the same error code and total ROLL-BACK?

Microsoft will force 22H2 on home PCs that hasn’t updated to 22H2.
Microsoft can’t force 22H2 on PCs with blocked updates (InControl, registry hacks…)

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Re:  “Microsoft can’t force 22H2 on PCs with blocked updates (InControl, registry hacks…)”

Good news (for a change)!  I didn’t think they could, but I might be wrong about that.

As such, GIVING UP means I can continue to use a very reliable and productive Windows 10 version 1909 with WinUpdateStop ENABLED.

I also have plenty of prior drive images to choose from, if MS decides to play dirty.

Also, not previously mentioned are the following:

I have legal obligations imposed by 18 U.S.C. 4 to maintain proper custody of records acquired during 7 years of technical assistance to a complex USCG homicide investigation. 

There is no statute of limitations for murder.

And, reader questions about that investigation are still being asked at various Internet social media platforms re: Maritime Safety Detachment / Sector San Juan / Virgin Islands.

Reply | Quote

Another option, not yet discussed, is a dual-boot system e.g. by doing a fresh install of the OEM DVD disc of 21H2 to a brand new SSD wired directly to the SATA0 port on the motherboard.

That DVD has been sitting in my spare parts, without being used, since August 2022.

That method will allow me to remove the RAID controller temporarily, so the 21H2 install process does not make any changes to the RAID-0 array hosting the current C: .

My best friend in Asia has adopted that approach:  dual-booting Linux and Windows 10

Reply | Quote

AVG Driver Updater reports drivers are updated:

Reply | Quote

Google “0xC1900101-0x20017”

today finds e.g.:

Created June 16, 2021  <— TWO (2) YEAR AGO

https://answers.microsoft.com/en-us/insider/forum/all/windows-update-fails-with-error-code-0xc1900101/31c3d970-759b-4f51-9a4c-96879788df44

NB:

“EDIT: If the only solution is a clean install, I’m probably going to wait a little while and just live without major updates for a few months. Feature updates and quality updates and other minor updates have been working fine, so I don’t think I’ll run into any security issues.”

AND:

“I looked at the logs, but could not find anything constructive. Usually 20017 is resolved by updating BIOS, but it doesn’t look like there is any new update available for the machine.”

[… AND Paul’s PC here has the latest BIOS and it can NOT revert to an older BIOS.]

Reply | Quote

BTW, did you try disabling all aspects of AVG and any other third-party anti-malware before updating? There have been problems in the past with anti-malware.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Thanks!

I have not installed any other AVG software on this PC.

I use the integrated Windows 10 “Virus and threat protection” on this PC.

This AVG Driver Updater was only installed a few days ago, to do an independent check of installed device drivers.

I thought that would help, given the majority of Prosumers who suspect the error code in question is caused by driver problems.

AVG Driver Updater did find a newer driver version number for the ViaLabs DW-VL805-4 controller on our USB 3.0 add-in card, and the only newer driver I could find caused a yellow bang sign “!”;  so, I had to revert that driver to a older working version.

So, this morning I removed that add-in card and replaced it with a new Vantec UGT-PC345 USB 3.0 adapter;  Windows 10 configured it automatically and installed the correct device driver without requiring user intervention.

I ran AVG Driver Updater after installing the new Vantec UGT-PC345, and that AVG Driver Updater is evidently happy with the driver which Windows 10 installed automatically.

 

Reply | Quote

Now that you’ve removed your older USB Hub in favor of a seemingly newer unit, and your third party driver update monitor is happy that you have the latest driver for that device (the USB Hub), why not try updating from 1909 one more time to see if it somehow no longer encounters the error you’ve been encountering.

After all, it could very well have been the driver for your older hub that was the actual culprit instead of your RAID driver as you had thought. Remember, you managed to update the RAID driver, but the same error code you had before the RAID driver update persisted, so maybe it WAS the driver you had for your older USB hub. “Weird” or unorthodox drivers (in the “eyes” of Windows) can sometimes create weird errors pointing to something separate from the actual cause. In your case, you had a Windows 7 driver installed on a device that Windows 10 was trying to run. That’s probably why you were getting the yellow triangle with the exclamation point when you were trying to update the driver…you trying to update one Windows 7 driver with yet a slightly newer Windows 7 driver and windows 10 wanted nothing of it. Files and drivers with versions that start out as 6.1.7600 are Windows 7’s built-in driver versions, and not meant for Windows 10. As has been pointed out higher up in this thread, Windows 10’s built-in drivers start out with version numbers 10.0.19041 and up, as does the driver for my USB 3.0 hub.

One more attempt at the upgrade from 1909 to 22H2 at least worth a try. You may very well get a pleasant surprise now that you’ve cleared up the driver issue for your USB 3.0 hub.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Re:  “you had a Windows 7 driver installed on a device that Windows 10 was trying to run. That’s probably why you were getting the yellow triangle”

Yes, that makes perfect sense.   🙂

The one website where I did find the latest driver for that former USB adapter must have downloaded the Windows 7 version;  and,

I must have tried to give Device Manager that driver file in error.

MANY THANKS for the confirmation.  That helps.

If Device Manager would merely UNINSTALL a device on demand, and NOT RE-INSTALL it after a RESTART.  This would help remove that “phantom driver” for PCI IDE devices.

FYI:  I already had a few of those Vantec UGT-PC345 USB 3.0 adapters:  from my experience to date, they are very reliable, and they support a 20-pin internal socket.

That 20-pin USB 3.0 socket can “branch” to 2 x Type-A USB females, with a compatible cable.

I’ve been buying a 6″ long Y-cable and inserting 2 x 256GB SanDisk USB 3.0 flash drives (cheap and plentiful storage for archiving systems-related files).

Those are also very convenient for storing working drive images of C: and they become part of the interior components that never need any maintenance, after being installed and formatted.

THANKS AGAIN!

Reply | Quote

Re:  “why not try updating from 1909 one more time to see if it somehow no longer encounters the error you’ve been encountering.”

Very sorry, I forgot to mention:

I already did that after installing and testing the new Vantec UGT-PC345:

SAME ERROR CODES!  ;-(

I might spring for this used PC at eBay:  lots of h/w + Windows 10 already installed

the photo of the inside shows a very clean interior

BIOS version is v02.05  <— will help to test presence of “phantom driver”

only ~$100 + free shipping:

https://www.ebay.com/itm/364133007227?hash=item54c804bf7b:g:mxwAAOSw04xj3YHw&amdata=enc%3AAQAIAAAA8CFq%2FyaABwSSSm3UigfvGUE5Aai7xR1IFJ2js%2BEJo%2FI3yi0zcLh%2BWazvC4iB7PbZNIOVGgHO11hKe6JCrovtFUZxpw%2BfG%2FLI3yNRbdzF17Y0h8Gl5HN8Ec7ig5fAHg15rmEy2jJMJUpcODAsO441CjRRLPx3bip9slMCGyqxrXgduI7yGFRCmrwbiadhjME%2FTpUnxFeD%2BPxCYeRx%2BdO30BVVDiBSo91gZldPyFsNRWQs2Atb4ClR25Ke88qutqaPOuQa2IIQKjfMNuGvCrK7Vt6rWuyFfdyjNiq5%2BoqjEVVO4tzuAowDFakgmFZIufx0Ng%3D%3D%7Ctkp%3ABk9SR4zI0sqMYg#readMoreDesc

Reply | Quote

another trial / another error:

After running Windows Update Assistant several times now, I tried it again by choosing the “media creation” option, and writing the “setup.exe” file etc. to a brand new USB 3.0 flash drive.

I initially formatted that SanDisk 256GB flash drive in NTFS format and did a quick test.

The Media Creation Tool then re-formatted it in FAT32 format.

Windows Update Assistant failed again with the exact same error codes and total ROLL-BACK.

But, I’ve also noticed a very distinct pattern, now worth mentioning because it has repeated:

After re-starting, I’ve noticed that a Network Drive letter gets re-assigned during each attempt with Windows Update Assistant.

After total ROLL-BACK, this bug required DISCONNECTING that Network Drive letter, re-starting again, and re-mapping that Network Drive letter to the correct remote shared partition.

Moreover, during the ROLL-BACK, I’ve also noticed that the drive activity light has been frequently blinking on the PC’s front panel.  That would ONLY happen if one of the on-board SATA ports were experiencing I/O for some reason.

That may be an important clue, because the C: system partition on this PC is hosted on a fast RAID-0 array, and the integrated SATA ports host 2 x JBOD SSDs, 1 x JBOD HDD and 1 x ODD (4 x SATA ports total, designated  SATA0, SATA1, SATA2, SATA3).

The latter SSDs and HDD are only used for data now, but there are “dual-boot” OS partitions on all three e.g. the original OS shipped by the MAR seller was hosted on the latter JBOD HDD.

As such, Windows Update Assistant may be losing track of drive letters and consequently gets confused at some point about what is supposed to go where (still just another theory).

 

Reply | Quote

I’ve also taken note of some Prosumers who recommended DISCONNECTING ALL PERIPHERALS — as an alternative to updating all active device drivers.

As such, one “ACID TEST” would be to disconnect all SATA cables, to disconnect all USB cables, and temporarily to remove all add-in cards EXCEPT FOR the one hosting the C: system partition.

Similarly, all Network Drive letters would need to be temporarily DISCONNECTED too.

Then, after a RESTART, Windows Update Assistant would be run with only 3 active drive letters:

C: for the OS stored in the primary partition on the RAID-0 array

E: for data stored in the secondary partition on the RAID-0 array

D: assigned to the USB flash drive with “setup.exe” etc. when it’s plugged in after RESTART

E: might also need to be removed temporarily, if doing so prevents any more drive letter confusions from happening

Reply | Quote

UNDIVIDED ATTENTION now 🙂

I feel as if I AM VERY CLOSE TO SOLVING THIS CHRONIC UPDATE PROBLEM:

Here’s more evidence to support the theory above re: drive letter confusions:

First, note how MiniTool’s excellent Partition Wizard does find drive letter G: assigned to the Recovery Partition, whereas Disk Management does NOT.

Secondly, the System Reserve partition presently has no drive letter assigned.

When I try to “Add” a drive letter to that System Reserve partition, NOTE WELL how Windows 10 version 1909 selects drive letter “T”.

HOWEVER, “T” has already been mapped to a shared partition on a Network drive !!!

When Windows Update Assistant has finished its total ROLL-BACK, drive letter “T” has a “boot” folder in it;  at that point “T” no longer maps to the correct shared partition on its network drive!

That’s clear evidence of one or more bugs in Microsoft’s Windows Update Assistant.

see 2 screenshots now …

 

Reply | Quote

Here’s Network drive letter “T” when correctly mapped to the correct shared partition on the correct Network drive:

Reply | Quote

WOW!

It’s no wonder why “DISCONNECTING ALL PERIPHERALS” was found to fix many of the problems that are occurring with Windows Update Assistant.

That system software fails to keep all Local and Network drive letters properly organized and assigned.

Network drive letters should remain TOTALLY OFF-LIMITS to Windows Update.

Reply | Quote

More support for the theory above:

On the identical PC where 22H2 updated AOK the first time, most of the System Reserve partitions have drive letters assigned;  only one System Reserve partition is lacking a drive letter.

the first image below is a partial screen shot of Windows Disk Management;

the second image below is a comparable screen shot of MiniTool Partition Wizard:

Reply | Quote

FALSE ALARM!  My deepest apologies.

It SURE felt like I had isolated at least one major problem.

I added drive letters to all of the System Reserve partitions, and then

I tried Windows Update Assistant with WinUpdateStop both DISABLED and ENABLED.

Both ways produced the EXACT SAME ERROR CODES.

Man oh man, is this frustrating.

Plus Memorial Day is always an occasion for great sadness in my life.

Thank you, again, for your patience with my ordeal here.

 

Reply | Quote

You have run 2 driver updaters and both have found no issue, ergo, there is no issue with drivers. It must be something else.

We have not suggested you buy a new SSD.
We have suggested you make an image backup, preferable to an external USB HDD (cheap). You should be doing this anyway.
Install over the top on the existing internal disk, then try the 22H2 update.

cheers, Paul

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Thanks, but I already tried all of those things.

I routinely save images of the C: system partition.

We did confirm a subtle bug in Windows Update Assistant:  after ROLL-BACK, the pop-up window says:

“We’ve set your PC back to the way it was right before you started installing Windows 10.”

That claim was NOT correct:  a Network drive letter ended up pointing to a different NTFS partition after total ROLL-BACK.

This bug strongly suggests that Windows Update Assistant is confusing drive letters, which has the potential to cause low-level havoc with system software in general.

To repair the damage, I had to DISCONNECT that Network drive letter, RESTART, and Map network drive again by pointing the correct drive letter to the correct shared partition on the Network drive.

Thanks anyway.

Reply | Quote

What is the current status?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Re:  “What is the current status?”

To focus on the “phantom driver” question, I purchased a refurbished version of the exact same motherboard and chassis:  HP Compaq Pro 6300 MT (mini-tower).

It came with Windows 10 21H2 pre-installed on a 128GB SSD, and the motherboard BIOS version is the same as the BIOS version on the problem PC.

It also came with a 2TB Seagate HDD in the second drive cage.

The CPU is a faster Core i7-3770 (4 cores / 8 threads).

The initialization phase went smoothly.

There is no “PCI IDE” controller or driver present anywhere in this refurbished PC e.g. in Device Manager.

I then added a 4-port SATA controller in one x1 expansion slot, and a 2.5GbE controller in the second x1 expansion slot.  Both are working AOK.

Still no “phantom driver” is visible anywhere.

Lastly, I ran Windows updates successfully and updated this PC to Windows 10 Version 22H2, Build 19045.3031 .

I’ve delayed any more Windows Updates for 35 days, using the Windows option for that purpose.

I’ve also played around with WinUpdateStop and the “Windows Update” entry in Services.

I’ve learned that “Windows Update Medic” may explain how Windows Update can still run even if the Services entry has been disabled and stopped.

I’m planning to try “Windows Update Blocker” which I only discovered yesterday.

My goal now is to freeze our Windows 10 PCs at 22H2 indefinitely (if possible).

Hope this helps.

1 user thanked author for this post.

geekdom

Reply | Quote

Windows 10 22H2 is the last version of Windows 10, so if they are not Windows 11 compatible and Microsoft does not change Windows 11 requirements they will not get more feature updates although monthly patches will continue.

Reply | Quote

SupremeLaW wrote:

My goal now is to freeze our Windows 10 PCs at 22H2 indefinitely (if possible).

There is no need to ‘freeze’ as 10 22H2 is the last version until EOL on 2025.
Your CPU isn’t Win11 compatible.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Re:  10 22H2 is the last version until EOL on 2025.

Thanks for that.

Re: Your CPU isn’t Win11 compatible.

Yes, that is also confirmed by Windows Update.

I appreciate your help.

Reply | Quote

We’ve recently had such good luck purchasing refurbished HP workstations, this company’s website advertises refurbished HP Z240 workstations with Windows 11 pre-installed:

https://pcserverandparts.com/workstations/hp-workstations/hp-z240-workstation/?_bc_fsnf=1&Operating+System=Windows+11+Professional+64-bit&Processor+Speed%5B%5D=3.20+GHz&Processor+Speed%5B%5D=3.40+GHz&Processor+Speed%5B%5D=3.60+GHz

In the past, they were happy to sell a custom configuration to us e.g. by pre-installing Windows 10 on an M.2 NVMe SSD installed in the integrated M.2 socket on that motherboard.

So, if at some point in the future we might need Windows 11, I would contact that company for advice, given that I’m already one of their existing customers.

And, Icy Dock now makes a large variety of SSD enclosures e.g. they now sell an 8-port enclosure for 2.5″ SSDs that fits perfectly in a standard 5.25″ external drive bay.  And, a 6-port enclosure also accommodates an Ultra Thin ODD in the same enclosure.

Reply | Quote

Thank you for your persistence in this matter and the detailed follow-up.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

SupremeLaW

Reply | Quote

You’re very welcome.

I started using computers in June 1971 — first year of grad school at U.C. Irvine.

I’ll be 75 this month.

Somewhere during many years of education, I also learned how to write.

I frankly disagree strongly with the stated MS policy of “FORCING” OS updates to 22H2.

And, documenting my experience, while trying to do so voluntarily, may be useful to others who are similarly situated, and/or to MS software engineers who are more than capable to appreciate what is written in this long and involved Topic here.

In one of the most recent replies above, I did summarize how Windows Update Assistant scrambled network drive letters: 

potentially, this is a symptom of a much deeper and much more serious problem which I was unable to fix.

That symptom did repeat several times, so it was not some random event.

If it helps anyone else reading here, we have a regular practice that runs “Migrate OS” in Partition Wizard, in order to have an OS clone which can be started by simply changing the Boot Order in the motherboard BIOS.

Restoring a working drive image of C: merely requires that one BIOS change to a backup boot drive.  Then, restore tasks using Acronis True Image WD Edition can run at full speed, because all device drivers are available in the migrated copy of the OS system files.

If I were an MS software engineer, I would suspect the scrambled network drive letters are connected somehow to backup copies of the OS that are stored on our secondary SSD(s) and/or secondary HDD(s).

The latter is a worthy hypothesis, chiefly because a few recommended solutions to the ROLL-BACK error code 0xC1900101-0x20017 required DISCONNECTING ALL PERIPHERALS.

Doing so would necessarily reduce the total number of drive letters that Windows Update Assistant needs to manage (and NOT “scramble”).

From my own many years of experience with Windows, confirming a scrambled network drive letter was enough to convince me to GIVE UP — at least with this “problem PC”.

1 user thanked author for this post.

Alex5723

Reply | Quote

Permit me to elaborate a little more on the “scrambled drive letters”:

We manage 4 different OS generations:  XP, 7, 8.1 and 10.

XP is needed for an older HP scanner that has no drivers for later versions of Windows.

8.1 is the OS that came with our only laptop, and it appears to work AOK.

The older OS versions are also now re-purposed as backup storage servers.

One very hard and fast rule we impose on that LAN is NEVER EVER to share C: on any PC hard-wired to that network.

Thus, drive letter “Z:” on all other PCs points to a shared data partition on one PC, which functions as a de facto “server” (but without running Windows Server OS).

Thus, in Command Prompt we run a custom BATCH program named “get” like this:

get website.org Z

is parsed to execute this BATCH command sequence:

E:
cd \
xcopy Z:\website.org website.org /s/e/v/d

 

After several trials with Windows Update and with Windows Update Assistant, Z: ended up pointing to a different partition which contained a “boot” folder.

That one fact was enough to raise a RED FLAG, a FLAG so serious that I did not even try to dig any deeper.  I could have tried to pinpoint where that “boot” folder was located on our LAN, but I decided against diving deeper.

Instead, I immediately DISCONNECTED Z:, RESTARTED and then re-mapped Z: to the correct remote partition.

Bottom Line:  not only are drive letters being scrambled;  the resulting scramble clearly resulted in a serious security violation — by pointing Z: to a UNshared partition somewhere on our LAN i.e. most probably a partition dedicated to Windows 10 “System Reserved” or “Recovery Partition”.

I have never ever created a “boot” folder anywhere on our LAN.

 

Reply | Quote

I found a “boot” folder in one of the System Reserved partitions.

This System Reserved partition is the first NTFS partition immediately in front of the C: system partition.

Disk Management says it’s 549 MB in size.

The “scrambled drive letter” ended up pointing to that System Reserved partition INSTEAD OF pointing properly to the correct shared partition on a Network Drive.

Here are the results of a DIR command, using Command Prompt in elevated mode:

Volume in drive Y is System Reserved
Volume Serial Number is 57F5-CB70

Directory of Y:\

05/29/2023 04:51 PM <DIR> Boot
0 File(s) 0 bytes
1 Dir(s) 539,021,312 bytes free

Reply | Quote

Y:
cd Boot
dir /ogn >dirlist.txt

writes the following file contents to dirlist.txt :

Volume in drive Y is System Reserved
Volume Serial Number is 57F5-CB70

Directory of Y:\Boot

05/29/2023 04:51 PM <DIR> .
05/29/2023 04:51 PM <DIR> ..
05/23/2023 10:48 AM <DIR> bg-BG
05/23/2023 10:48 AM <DIR> cs-CZ
05/23/2023 10:48 AM <DIR> da-DK
05/23/2023 10:48 AM <DIR> de-DE
05/23/2023 10:48 AM <DIR> el-GR
05/23/2023 10:48 AM <DIR> en-GB
05/23/2023 10:48 AM <DIR> en-US
05/23/2023 10:48 AM <DIR> es-ES
05/23/2023 10:48 AM <DIR> es-MX
05/23/2023 10:48 AM <DIR> et-EE
05/23/2023 10:48 AM <DIR> fi-FI
01/07/2020 08:34 PM <DIR> Fonts
05/23/2023 10:48 AM <DIR> fr-CA
05/23/2023 10:48 AM <DIR> fr-FR
05/23/2023 10:48 AM <DIR> hr-HR
05/23/2023 10:48 AM <DIR> hu-HU
05/23/2023 10:48 AM <DIR> it-IT
05/23/2023 10:48 AM <DIR> ja-JP
05/23/2023 10:48 AM <DIR> ko-KR
05/23/2023 10:48 AM <DIR> lt-LT
05/23/2023 10:48 AM <DIR> lv-LV
05/23/2023 10:48 AM <DIR> nb-NO
05/23/2023 10:48 AM <DIR> nl-NL
05/23/2023 10:48 AM <DIR> pl-PL
05/23/2023 10:48 AM <DIR> pt-BR
05/23/2023 10:48 AM <DIR> pt-PT
05/23/2023 10:48 AM <DIR> qps-ploc
05/23/2023 10:48 AM <DIR> qps-plocm
01/07/2020 08:34 PM <DIR> Resources
05/23/2023 10:48 AM <DIR> ro-RO
05/23/2023 10:48 AM <DIR> ru-RU
05/23/2023 10:48 AM <DIR> sk-SK
05/23/2023 10:48 AM <DIR> sl-SI
05/23/2023 10:48 AM <DIR> sr-Latn-RS
05/23/2023 10:48 AM <DIR> sv-SE
05/23/2023 10:48 AM <DIR> tr-TR
05/23/2023 10:48 AM <DIR> uk-UA
05/23/2023 10:48 AM <DIR> zh-CN
05/23/2023 10:48 AM <DIR> zh-TW
06/10/2023 04:24 PM 40,960 BCD
05/23/2023 10:41 AM 27,448 bootuwf.dll
05/23/2023 10:41 AM 99,664 bootvhd.dll
05/23/2023 10:41 AM 990,032 memtest.exe
4 File(s) 1,158,104 bytes
41 Dir(s) 539,021,312 bytes free

Reply | Quote

And, after total ROLL-BACK, Windows Update Assistant finishes by reporting:

“The installation failed in the SAFE-OS phase with an error during BOOT  operation.”

“We’ve set your PC back to the way it was right before you started installing Windows 10.”

If the latter were true and correct, the existing Network drive letter would remain intact i.e. still pointing to the correct shared partition on a Network drive.

But, instead that Network drive letter points to a System Reserved partition which contains a “Boot” sub-folder (as explained in more detail above).

Reply | Quote

You have assigned drive letters to partitions that should not have drive letters. This is bad m’kay.

Remove the drive letters from O, V, W, F, S, P, K & I.

Try again.

cheers, Paul

1 user thanked author for this post.

SupremeLaW

Reply | Quote

That was another experiment to test another hypothesis, to compare it to a SFF version of the same motherboard on which 22H2 installed AOK the first time.

I also needed to assign drive letters, to make it possible to inspect the files stored in those partitions.

I can try removing those extra drive letters, but the error code in question did occur BEFORE I tried assigning drive letters to “System Reserved” etc.

I’ve honestly become quite weary of so many trials-and-errors, with no end in sight.

I still have no answers to explain “phantom driver” — “PCI IDE” controller.

As I believe I already mentioned, my BEST GUESS is that the original owner may have installed a PCI add-in card to add a 40-pin PATA socket.  Someone probably removed that add-in card withOUT using Device Manager to remove the driver too.

If that PCI IDE driver was not properly coded way back then, it may be “stuck” somewhere in the C: system partition, and the current Plug-and-Play logic is erring by installing it during STARTUP even though no add-in-card is installed in the PCI expansion slot.

Thanks for your patience!

Reply | Quote

That set of drive letters are assigned on Paul26 — the SFF version of the same motherboard on which 22H2 installed AOK.

That set of drive letters are NOT the same on Paul27 — the problem PC.

Correct me if I am wrong:

you advise REMOVING drive letters from all “System Reserved” partitions, and from backup (“cloned”) OS partitions which would be assigned drive letter C: when booting from one of those cloned OS partitions.

I started Paul26 (where 22H2 installed AOK the first time), and confirmed the following:

Paul26
Disk Management:

O: Disk 0 System Reserved
V: Disk 1 System Reserved
W: Disk 1 OS
F: Disk 2 System Reserved
S: Disk 2 OS
P: Disk 3 OS
K: Disk 4 System Reserved
I: Disk 4 OS

Your list was truncated because my screenshot was truncated, 
due to the max resolution of this monitor.

Reply | Quote

I’ve “normalized” all drive letters now on the problem PC (“Paul27”).

There are no drive letters assigned to any System Reserved partitions.

There are no drive letters assigned to any of the “cloned” OS partitions.

I had to RESTART twice to get Windows 10 to settle down, but Paul27 is still operating correctly after the second RESTART.

On all active drive letters, I ran the following in Command Prompt with no errors detected:

chkdsk [L:] /v

where,

“L” = Windows drive “L”etter

Does your theory predict that Windows Update Assistant will upgrade to 22H2 now, without the nagging error codes?

p.s.  I’m dubious because:

Windows internals, particularly Windows Update code, should automatically create a complete table of active partitions, whether or not any one partition has been assigned a drive letter.

Windows Disk Management does this out of sheer necessity!

As such, Windows internal code should have full access to all files in any one partition to which a drive letter has NOT yet been assigned.

Also, the tests I have already run to date appear to prove that assigning drive letters to System Reserved and cloned OS partitions made no difference whatsoever:  the SFF PC wth the exact same motherboard updated AOK to 22H2 the first time.

Reply | Quote

I got the same error code and ROLL-BACK (see screenshot below).

HOWEVER, after “normalizing” all of the drive letters, there are noticeable differences after doing so.

(1)  the Network drive letter is still intact now (NOT scrambled);

(2) in Disk Management, the first “System Reserved” partition was assigned drive letter G:

(3) however, Partition Wizard says drive letter H: was assigned to that first partition in (2);

(4) after RESTARTING again, both Disk Management and Partition Wizard say there is no drive letter assigned to the first partition in (2).

Bottom Line:  albeit subtle, there does still appear to be a bug in drive letter assignments being done by Windows Update Assistant, when attempting to update to 22H2.

 

Reply | Quote

Re:  “We’ve set your PC back to the way it was right before you started installing Windows 10.

The latter is still misleading.

I can see why Windows Update Assistant might need to assign a drive letter to the first System Reserved partition, for some reason required by OS systems programming.

However, if Windows Update Assistant decides to ROLL-BACK completely, it should REMOVE that drive letter from the first System Reserved partition.

Leaving a new drive letter assigned to that System Reserved partition clearly conflicts with the advisory that the PC has been set “back to the way it was”.  NO, NOT TRUE!

 

Reply | Quote

Here’s another apparent bug, this time in the Windows Disk Management utility:

The Recovery Partition on Disk 1 is the third partition in sequence on that Disk 1.

But, at the top see where it states that this partition is the fourth in sequence on Disk 1.

We double-checked that Recovery Partition, and ZERO space is allocated before it and ZERO space is allocated after it.  Same is true of the other partitions on Disk 1.

These allocations were triple-checked with Partition Wizard, using the RESIZE function:  that option reports the unallocated space before and after any given partition.

Reply | Quote

Removing the extra drive letters was to stop your drive letters messing up, and it worked as expected.

Don’t worry about where the small partitions are, it’s not relevant and you have not lost any space worth regaining.

The upgrade issue is with the Windows installation, which is why we suggested an “over the top” reinstall. It’s either that or a complete reinstallation.

cheers, Paul

Reply | Quote

It still assigned “G” to the first System Reserved partition on Disk 0.

Another RESTART was required to remove G: .

FYI:  I already tried “over the top” and that too failed.

And, today’s try using Windows Update Assistant failed again — same way.

There are just too many third-party programs on my desktop — 35 and counting — to contemplate re-installing all of them.  Some also have paid licenses, which might entail even more time-consuming fiddling.

And, I require working FTP to continue maintaining a large website.

As of right now, I have switched to “Windows Update Blocker” because it also locks “Windows Update Medic Service” — unlike the other WinUpdateStop program I had been using:

https://www.sordum.org/9470/windows-update-blocker-v1-8/

The fundamental GOOD NEWS is that this PC continues to function correctly for my needs.

And, I now have identical spare hardware, on which I can fall back if this PC fails permanently.  That spare did Update to 22H2 first try, and there is no “phantom PCI IDE device” on that spare.

Over the next year or so, I can add storage to the latter spare:  it also has a faster Core i7-3770, which has 4 CPU cores with hyper-threading, for a total of 8 threads.

Many thanks for all your help to date.

Reply | Quote

I can’t see where you tried the “over the top” installation. Can you point it out?

Did you follow these steps?
1. Download Windows 22H2 ISO from MS.
2. Double click on the ISO to have Windows mount it.
3. Run setup.exe from the mounted ISO.

cheers, Paul

1 user thanked author for this post.

SupremeLaW

Reply | Quote

I may have misunderstood you.

I’ve tried 4 different methods of updating to 22H2:

(1)  regular Windows Update (Check for updates)

(2) option 1 in Windows Update Assistant (Update now)

https://www.microsoft.com/en-us/software-download/windows10

(3) option 2 in Windows Update Assistant (setup.exe on a USB stick)

(4) install of 21H2 from OEM DVD purchased last August 2022, preserving data and applications, to be followed by trying Windows Update / Check for updates.

If there is a fifth method which you call “over the top”, i.e. ISO etc., then No I have not done that.

Reply | Quote

Here’s the output of a DIR command on the USB stick created by option 2 in Windows Update Assistant:

Directory of A:\

05/29/2023 11:17 AM <DIR> boot
05/29/2023 11:17 AM <DIR> efi
05/29/2023 11:17 AM <DIR> sources
05/29/2023 11:19 AM <DIR> support
05/05/2023 10:24 AM 128 autorun.inf
05/05/2023 10:24 AM 413,738 bootmgr
05/05/2023 10:24 AM 1,572,208 bootmgr.efi
05/05/2023 10:24 AM 74,184 setup.exe
4 File(s) 2,060,258 bytes
4 Dir(s) 29,517,152,256 bytes free

Reply | Quote

Please follow this scenario, if you have the time, to see if it makes any sense to you:

Begin by recalling several Internet searches which found advice that the error codes in question typically result from incompatible device drivers:

(1)  this motherboard has 1 x legacy PCI expansion slot (for legacy ATA-133 devices)

(2)  when it was brand new, PATA HDDs were still in more frequent use

(3)  this motherboard was designed and built with no integrated PATA socket or IDE controller, and there are no 40-pin PATA sockets anywhere on this motherboard

(4)  HP may have offered a custom PCI add-in card with 1 or 2 x 40-pin PATA sockets

(5)  that PCI add-in card was installed in this motherboard at one point in the past

(6)  this PC was later sold to a Microsoft Authorized Refurbished (“MAR”) with that add-in card still installed

(7)  MAR staff physically removed that PCI add-in card, but without using Device Manager to remove the related device driver files:  this would happen if MAR purchased a bulk of many PCs, and to save time MAR staff did not STARTUP each PC to access Device Manager

(8)  those device driver files did not comply completely with MS policies for properly “signed” drivers

(9)  consequently what remained, after the add-in card was moved, are a set of defunct and obsolete driver files for the “Standard Dual Channel PCI IDE controller” that was on-board that add-in card

(10)  for some strange reason, Windows 10 Plug-and-Play continues to detect a hardware controller that requires those driver files, EVEN THOUGH that add-in card is no longer installed in the one legacy PCI expansion slot

(11)  the proof of (10) above is the result that occurs whenever that “Standard Dual Channel PCI IDE Controller” is UNINSTALLED with Device Manager:  during the next RESTART, that “PCI IDE” device is detected by Windows Plug-and-Play and shows up again despite being UNINSTALLED before the RESTART

(12) it might be possible to purchase a similar PCI IDE add-in card with PATA socket, but the existing driver files may not include the matching driver for that add-in card.

(13)  one test I can try, time permitting, is to install a standard Intel Gigabit PCI NIC in that one legacy PCI expansion slot;  the theory of this test is that Windows 10 will install the correct “signed” driver for that NIC, and retire the phantom “Standard Dual Channel PCI IDE Controller” permanently.

(14)  the test at (13) is relatively easy to perform, because there is nothing installed in that one legacy PCI expansion slot;  that chassis slot is currently populated with a small exhaust fan to help cool the Highpoint RAID controller installed in the x16 expansion slot that is right next to that PCI expansion slot.

That’s my relatively complex theory about this “phantom driver” that refuses to disappear.

Reply | Quote

I have now installed a very standard and reliable Intel Pro/1000 Desktop Adapter in the 1 x PCI expansion slot, after ENABLING that slot in the motherboard BIOS.

Windows 10 detected that add-in card correctly, and installed the correct device driver.

Now, Device Manager is showing even more anomalies under the IDE ATA/ATAPI controllers, with “Show hidden devices” also enabled:

there are now 2 x ATA Channel 0

there are now 2 x ATA Channel 1

only one of those pairs changes status when the Standard Dual Channel PCI IDE Controller is ENABLED:

—————————————————————————————–

—————————————————————————————–

—————————————————————————————–

 

 

Reply | Quote

Stop trying to find a potentially non-existent issue.

Make a full image backup.
Boot from a Windows USB.
Install from scratch.
Update to 22H2 – if required.
Restore your image and get back to work.
Report results.

cheers, Paul

Reply | Quote