So we are moving along pretty good with our W10 1607 > 1709 upgrade via SCCM
task sequence, mostly still in the IT deployment / Business pilot phase. I had
a user contact me yesterday telling me the update failed so I did the usual
digging through the log files in the panther directory and I found failure
pretty quickly. There were 4 applications listed as hard blocks in the
compatdata.xml file as shown below. I figured easy I will just remove the
programs and go about my day or so I thought. I started poking around on the
users machine and I couldn't find any of the programs Windows was complaining
about installed, nor could I even find a file or registry key that matched
those programs.
</DriverPackages><Programs><Program Name="Dell Storage Manager Driver - Please
read Microsoft Knowledge Base article: 941024" Id=""
IconId="afamgt.sys|56853beb5c5b62af"><CompatibilityInfo BlockingType="Hard"
StatusDetail="UpgradeBlock"/><Action Name="ManualUninstall" DisplayStyle="Text"
ResolveState="NotRun"/></Program>
<Program Name="VirusScan 8" Id=""
IconId="mcconsol.exe|b007179cc8857bb1"><CompatibilityInfo BlockingType="Hard"
StatusDetail="UpgradeBlock"/><Action Name="ManualUninstall" DisplayStyle="Text"
ResolveState="NotRun"/></Program>
<Program Name="WinZip 6.3-8.0" Id=""
IconId="winzip32.exe|5fcfbec786378e70"><CompatibilityInfo BlockingType="Hard"
StatusDetail="UpgradeBlock"/><Action Name="ManualUninstall" DisplayStyle="Text"
ResolveState="NotRun"/></Program>
<Program Name="WinZip 6.3-8.0" Id=""
IconId="winzip32.exe|76f8a8328e159eb8"><CompatibilityInfo BlockingType="Hard"
StatusDetail="UpgradeBlock"/><Action Name="ManualUninstall" DisplayStyle="Text"
ResolveState="NotRun"/></Program></Programs></CompatReport>
I started digging deeper and found another log file in the panther directory
called 2kP-xumRk0W++Fnb.3.8.0.0_APPRAISER_HumanReadable.xml that had some
additional information in it like where the program that was being blocked was
located. So it turn out all of the programs that Windows was finding and
causing the 1709 upgrade block are files buried out on a network drive that
everyone in the company has mapped? Why would the compat scan search mapped
network drives for program compatibility, this can't be the expected behavior
can it?
<Property Name="LongPathHash" Value="winzip32.exe|5fcfbec786378e70" />
<Property Name="LowerCaseLongPath" Value="\\MY FILE
SERVER\data\philproc\coke\winzip32.exe" />
<Property Name="LongPathHash" Value="winzip32.exe|6e5d59793305967c" />
<Property Name="LowerCaseLongPath" Value="\\MY FILE SERVER\data\tom
ragan pictures\tomacelli\winzip\winzip32.exe" />
<Property Name="LongPathHash" Value="afamgt.sys|56853beb5c5b62af" />
<Property Name="LowerCaseLongPath" Value="\\MY FILE
SERVER\data\bthompson\helpdesk\pcs stuff\i386\afamgt.sys" />
<Property Name="SdbAppName" Value="Dell Storage Manager Driver - Please read
Microsoft Knowledge Base article: 941024" Ordinal="1" />
<Property Name="LongPathHash" Value="mcconsol.exe|b007179cc8857bb1" />
<Property Name="LowerCaseLongPath" Value="\\MY FILE
SERVER\data\jrandolph\program files\network associates\virusscan\mcconsol.exe"
/>
<Property Name="SdbAppName" Value="VirusScan 8" Ordinal="1" />
Here is the command line that my OS upgrade TS runs -
Command line of Windows Setup upgrade: '"C:\windows\ccmcache\18\SETUP.EXE"
/ImageIndex 3 /auto Upgrade /quiet /noreboot /postoobe
"C:\windows\SMSTSPostUpgrade\SetupComplete.cmd" /postrollback
"C:\windows\SMSTSPostUpgrade\SetupRollback.cmd" /DynamicUpdate Disable /compat
IgnoreWarning /compat ScanOnly
Here is what I get when I run the setup.exe manually from the ccmcache
directory.
[cid:image001.png@01D39680.65CDE910]
