Determining what’s blocking Windows 10 2004

Topic

New Reply

UPGRADING WINDOWS By Susan Bradley Whenever Microsoft releases a new version of Windows 10, days, weeks, and even months can pass before the upgrade s
[See the full post at: Determining what’s blocking Windows 10 2004]

5 users thanked author for this post.

Elly, tcc089, abbodi86, geekdom, woody

Reply | Quote

Replies

I completed the first step, Determining setup issues. As stated and a paraphrase, compatibility files didn’t give a clear direction of what would block an upgrade.

At the current time, I am unwilling to take the next step which is an upgrade attempt.

What was troubling was the final remediation step: find more disk space. In what fashion will waiting until your device is ready for it solve the problem of too little disk space? Does Microsoft intend to “clear a path” through existing files on the system?

My problem may be different from the problem described here, but it strikes me that remediation requires action on the part of the user, not Microsoft. And for that remediation to occur requires clear user-friendly diagnostic documentation.

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

Reply | Quote

[tcc089]

Thanks Susan, for an incredibly helpful article.

I did the first steps by running Setup in “/compat scanonly” mode.  When I then ran SetupDiag to interpret the resulting log files, all it said was:

<FailureData>If you wish to update this system, remove the /Compat ScanOnly switch from the command line.</FailureData>
<FailureDetails />
<Remediation>For more information about Setup command line switches, see here:
“https: //docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options” </Remediation>

In other words, it just told me that I had to try a real upgrade before it was going to help me diagnose the issue stopping said upgrade.

As with the previous poster, and aligning closely to Woody’s advice, I am not willing to attempt the upgrade for real as yet.

Any thought perhaps?  Thanks.

• This reply was modified 2 years, 9 months ago by tcc089. Reason: Attempt to remove hyperlink within error text

1 user thanked author for this post.

geekdom

Reply | Quote

[geekdom]

Windows Update Assistant presents this information:

Windows Update presents this information:

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

• This reply was modified 2 years, 9 months ago by geekdom.
• This reply was modified 2 years, 9 months ago by geekdom.
• This reply was modified 2 years, 9 months ago by geekdom.

Reply | Quote

When I inserted two pictures at the same time in the above post, the first picture was omitted and a picture I don’t have and had not seen was included in my post. I edited my post and again included my picture in the post. The picture I don’t have and did not submit then disappeared from my post. Please check include picture capabilities.

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

Reply | Quote

I returned to Determining setup issues, ran the command again, and checked the logs. The most useful log was:
C:\Temp\Logfiles.log\Panther\ScanResult.xml

This log indicated that two driver packages were blocking migration. Those packages were located and removed, but the message in the log persists with the same two driver packages flagged as blocking migration. All else appears compatible.

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

1 user thanked author for this post.

tcc089

Reply | Quote

I too decided to try the Determine setup issues commands again.  Using your recommendation @geekdom to concentrate only on the resultant C:Temp\Logfiles.log\Panther\ScanResult.xml file, I now noticed that there were two lines that looked like the culprits:

<DriverPackage Inf=”oem78.inf” BlockMigration=”True” HasSignedBinaries=”False”/><DriverPackage Inf=”oem77.inf” BlockMigration=”True” HasSignedBinaries=”False”/>

I looked these up in the C:\Windows\INF folder.  I was somewhat surprised to see that Oem77 related to the Driver Package for “Microsoft Print To PDF”, and Oem78 was for the “Microsoft XPS Document Writer v4” driver.

So, I assume I must conclude that the reason the upgrade is blocked is due to two of Microsoft’s own driver software packages!

Phew!

1 user thanked author for this post.

geekdom

Reply | Quote

tcc089 wrote:

I looked these up in the C:\Windows\INF folder.  I was somewhat surprised to see that Oem77 related to the Driver Package for “Microsoft Print To PDF”, and Oem78 was for the “Microsoft XPS Document Writer v4” driver.

I have looked at those .inf files too.
On my 1909 pro OEM77 is Intel TEE_Files_Driver.
OEM78 is a Realtek driver/dll

1 user thanked author for this post.

tcc089

Reply | Quote

[geekdom]

The oem numbers for each device vary from machine to machine.

Here are my two problem devices:

oem31.inf “Microsoft XPS Document Writer v4”
oem30.inf “Microsoft Print To PDF”

Different numbers, same Microsoft problem devices.

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

• This reply was modified 2 years, 9 months ago by geekdom.

1 user thanked author for this post.

Alex5723

Reply | Quote

Alex5723 wrote:

tcc089 wrote:

I looked these up in the C:\Windows\INF folder.  I was somewhat surprised to see that Oem77 related to the Driver Package for “Microsoft Print To PDF”, and Oem78 was for the “Microsoft XPS Document Writer v4” driver.

I have looked at those .inf files too.
On my 1909 pro OEM77 is Intel TEE_Files_Driver.
OEM78 is a Realtek driver/dll

what kind of Realtek driver? Realtek LAN, bluetooth, WLAN, audio?

better use DriverStore Explorer (RAPR.exe) to “decode” some of those OEM*.INF files

Reply | Quote

Hi @Alex5723 – thanks for pointing that out, and thanks @geekdom for confirming the different numbering of the OEMnn .Inf files.  That makes very good sense since each OEM will assign installation packages using their own process and enumeration/nomenclature.

@Alex5723, are you also getting the Block Upgrade message?  And have you tried Susan Bradley’s method of Determining the blocking problem issues (as @geekdom and I have done)?  If so, what was your result, i.e. did you isolate what’s blocking your upgrade?

I still find it interesting that the issue of Blocked Upgrade is because of two MS driver packages for both you @geekdom and me!

Reply | Quote

tcc089 wrote:

are you also getting the Block Upgrade message?  And have you tried Susan Bradley’s method of Determining the blocking problem issues
I still find it interesting that the issue of Blocked Upgrade is because of two MS driver packages for both you @geekdom and me!

I got the block message but didn’t run the test. There is no hurry in upgrading to 2004 (deferred for 365 days).
I find it more interesting that Microsoft doesn’t state the block reasons in its block notice.

Reply | Quote

Yes, I agree – as I mentioned above, like @geekdom, I am in no to rush to do this upgrade either.

Cheers!

Reply | Quote

These two problem devices have been uninstalled in multiple ways. They always return on reboot. The don’t show in devices, but they are in C:\Windows\INF and C:\Windows\System32\CatRoot\

Here are my two problem devices:

“Microsoft XPS Document Writer v4”
“Microsoft Print To PDF”

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

Reply | Quote

[EP]

you can not uninstall them with “conventional” methods.

maybe only DriverStore Explorer can “remove” the corresponding INF files (and their drivers)

for “Microsoft Print to PDF” look for prnms009.inf and uninstall that from Driverstore Explorer (use “force deletion” option if necessary) by clicking on the Delete Driver button

“for Microsoft XPS Document Writer” look for prnms001.inf and remove that from RAPR

• This reply was modified 2 years, 9 months ago by EP.
• This reply was modified 2 years, 9 months ago by EP.

Reply | Quote

Correct link as yours points to WUMgr:
https://github.com/lostindark/DriverStoreExplorer

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

Reply | Quote

[EP]

DOH! my bad.

In removing XPS Document Writer (and possibly Print to PDF), I should have suggested or have a look at this (it’s listed in the Windows features section which can be officially removed there instead of using DriverStore Explorer):

https://www.ghacks.net/2016/05/18/remove-microsoft-xps-document-writer-printer/

• This reply was modified 2 years, 9 months ago by EP.

Reply | Quote

[geekdom]

Features was attempted yesterday. The boxes are unchecked, but the two drivers remain.

devcon was installed and tried yesterday as well.

MajorGeeks supplied an executable of DriveStoreExplorer RAPR; this program will not permit uninstallation of those two drivers, although I cleaned out some old, unused drivers.

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

• This reply was modified 2 years, 9 months ago by geekdom.

Reply | Quote

Further exploration:

• The two problem devices, “Microsoft XPS Document Writer v4”  and “Microsoft Print To PDF” were removed via registry edit.
• Canon printer drivers were installed again.
• Intel drivers were updated again.
• Plenty of rebooting occurred between each of the above steps.
• I returned to Determining setup issues, ran the command again, and checked the logs.  C:TempLogfiles.logPantherScanResult.xml showed no errors. In checking other logs, I saw no obvious errors.
• On viewing Windows update, this message still appears:
• 

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

Reply | Quote

Thanks for the further analysis.  However, I am standing by my last statement.  I’m in no hurry, so I’ll let my laptop stay on 1909 until we get something definitive from MS.  Cheers!

1 user thanked author for this post.

geekdom

Reply | Quote

I’m waiting to patch as there are numerous documented errors associated with this upgrade. When this upgrade eventually makes an arrival, I will hide it.

I’m also curious about the reasons for blocking the upgrade on my system.

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

Reply | Quote

[tcc089]

Yikes, I think I might be now “worthy” all of a sudden, and I didn’t do anything!  Today (Jun 28) I now get this different message from last time:

“The Windows 10 May 2020 Update is on its way. Once it’s ready for your device, you’ll see the update available on this page.”

The older message contained the phrase: “…your device isn’t quite ready…“, but not today, now showing the above message instead.

I have read that some 1909 users have been upgraded (magically!) without their permission, i.e. they didn’t actuate the upgrade, it simply did it on its own.  So, is there a way to ensure a deferral for this on Win 10 Home?

Thanks.

• This reply was modified 2 years, 9 months ago by tcc089.

Reply | Quote

This registry key may also prevent upgrade for the Windows home version:

https://www.askwoody.com/forums/topic/win10-version-2004-deferrals-gone-from-the-user-interface-but-theres-a-little-known-registry-key-thatll-keep-new-versions-off-your-machine/

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

1 user thanked author for this post.

tcc089

Reply | Quote

tcc089 wrote:

I think I might be now “worthy” all of a sudden

Nothing has changed, just a new tweaked notice to calm all the millions who got the impression that their PC is broken.

1 user thanked author for this post.

tcc089

Reply | Quote