Windows 10 upgrade from 1803 to 2004
Hi all
We start with our pilot and migrating user from Windows 10 1803 to 2004.
We have created a Windows 10 2004 Managed Installation and we have with a few user problem to install the update.
We have DELL 7490 und 7390 2 in 1 .
Unter C:\$WINDOWS.~BT\Sources\Panther\setuperr.log we see this error msg:
2020-08-06 11:55:52, Error MOUPG CMoSetupOneSettingsHelperT<class CEmptyType>::GetSettingsParameters(209): Result = 0x8000000A
2020-08-06 11:56:13, Error CSI 00000001 (F) STATUS_OBJECT_NAME_NOT_FOUND #10# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysQueryValueKey(flags = 0, key = acc ('\REGISTRY\MACHINE\SYSTEM\Setup'), vn = [l:7 ml:8]'Compact', kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
2020-08-06 11:56:13, Error CSI 00000002 (F) STATUS_OBJECT_NAME_NOT_FOUND #9# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:31]'\Registry\Machine\SYSTEM\Setup\', vn = [l:7 ml:8]'Compact', ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
2020-08-06 11:56:28, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1253): Result = 0xC1800104[gle=0x00000002]
2020-08-06 11:56:28, Error MOUPG CDlpTask::CheckUserInterruptEx(3060): Result = 0x800704D3
2020-08-06 11:56:28, Error MOUPG CDlpTask::CheckUserInterrupt(3112): Result = 0x800704D3
2020-08-06 11:56:28, Error MOUPG CSetupManager::ExecuteInstallMode(839): Result = 0x800705BB
2020-08-06 11:56:28, Error MOUPG CSetupManager::ExecuteDownlevelMode(409): Result = 0x800705BB
2020-08-06 11:56:29, Error MOUPG CSetupManager::Execute(294): Result = 0x800705BB
2020-08-06 11:56:29, Error MOUPG CSetupHost::Execute(433): Result = 0x800705BB
2020-08-06 11:56:37, Error MOUPG CMoSetupOneSettingsHelperT<class CEmptyType>::GetSettingsParameters(209): Result = 0x8000000A
2020-08-06 11:56:50, Error CSI 00000001 (F) STATUS_OBJECT_NAME_NOT_FOUND #38# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysQueryValueKey(flags = 0, key = b08 ('\REGISTRY\MACHINE\SYSTEM\Setup'), vn = [l:7 ml:8]'Compact', kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
2020-08-06 11:56:50, Error CSI 00000002 (F) STATUS_OBJECT_NAME_NOT_FOUND #37# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:31]'\Registry\Machine\SYSTEM\Setup\', vn = [l:7 ml:8]'Compact', ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
2020-08-06 11:56:51, Error CSI 00000003 (F) STATUS_OBJECT_NAME_NOT_FOUND #68# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysQueryValueKey(flags = 0, key = b1c ('\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion'), vn = [l:23 ml:24]'BaseBuildRevisionNumber', kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
2020-08-06 11:56:51, Error CSI 00000004 (F) STATUS_OBJECT_NAME_NOT_FOUND #67# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:63]'\Registry\Machine\SOFTWARE\Microsoft\Windows NT\CurrentVersion\', vn = [l:23 ml:24]'BaseBuildRevisionNumber', ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
2020-08-06 11:56:52, Error CSI 00000005 (F) STATUS_OBJECT_NAME_NOT_FOUND #80# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysQueryValueKey(flags = 0, key = b20 ('\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts'), vn = [l:21 ml:22]'Arial Nova (TrueType)', kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
2020-08-06 11:56:52, Error CSI 00000006 (F) STATUS_OBJECT_NAME_NOT_FOUND #79# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:69]'\Registry\Machine\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts\', vn = [l:21 ml:22]'Arial Nova (TrueType)', ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
2020-08-06 11:57:16, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
2020-08-06 12:00:28, Error CONX Unable to get message handle 80092009 c:\windows\system32\drivers\tap0901.sys
2020-08-06 12:00:33, Error CONX 0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]
2020-08-06 12:01:25, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::Suspend(1253): Result = 0xC1800104
2020-08-06 12:01:25, Error MOUPG CDlpTask::CheckUserInterruptEx(3060): Result = 0x800704D3
2020-08-06 12:01:25, Error MOUPG CDlpTask::CheckUserInterrupt(3112): Result = 0x800704D3
2020-08-06 12:01:26, Error MOUPG CSetupManager::ExecuteInstallMode(868): Result = 0xC1900208
2020-08-06 12:01:26, Error MOUPG CSetupManager::ExecuteDownlevelMode(410): Result = 0xC1900208
2020-08-06 12:01:27, Error MOUPG CDlpTask::Cancel(982): Result = 0xC1800104[gle=0x00000003]
2020-08-06 12:01:27, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::CheckInitialized(237): Result = 0x8000000A[gle=0x00000003]
2020-08-06 12:01:27, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::Cancel(163): Result = 0x8000000A[gle=0x00000003]
2020-08-06 12:01:27, Error MOUPG CDlpTask::Cancel(1033): Result = 0x8000000A[gle=0x00000003]
2020-08-06 12:01:27, Error MOUPG CDlpManager::Reset(1662): Result = 0x8000000A[gle=0x00000003]
2020-08-06 12:01:27, Error MOUPG SetupManager: Reset WinDlp State failed with error [0x8000000A][gle=0x00000003]
2020-08-06 12:01:27, Error MOUPG SetupManager: Failed requested cleanup: [0x8000000A][gle=0x00000003]
2020-08-06 12:01:28, Error MOUPG CSetupManager::Execute(295): Result = 0xC1900208[gle=0x00000003]
2020-08-06 12:01:28, Error MOUPG CSetupHost::Execute(433): Result = 0xC1900208[gle=0x00000003]
Answers (4)
can you describe the MI you created?
According to your words it seems to work on some machines. Is this correct? Or did I misunderstoood you?
Comments:
-
We have used this guide https://www.itninja.com/blog/view/windows-10-feature-update. Right. It works on some machines.
For example. We start with 15 machines. All have the same build Windows 10 1803 Enterprise. 10 Machines were successful and 5 not. - DeepM 3 years ago
Please give this method a try and let me know how it goes: https://www.itninja.com/blog/view/windows-10-out-of-date-build-report-install-script
My team uses this in production for every feature update and it has worked well.
Edit: One way to narrow down whether it's KACE causing the failure or the machine's environment would be to run the upgrade manually (see the link I sent you, you would just run the .cmd file as admin locally on the machine). If it still does not work, then you know that it's something system-related. What I've found that works to resolve system-related failure issues include:
1. Update all drivers to the latest version
2. Copy the folder with the installer to the local machine.
3. msconfig -> Services tab -> Check box to "Hide all Microsoft services" then "Disable all", reboot, and try again using the local administrator account
If neither work, try launching command prompt as administrator and:
dism.exe /online /cleanup-image /restorehealth
Once that completes, run:
sfc /scannow
Comments:
-
Hi,
Many thanks for the link. We will take a look.
I think we found the problem.
Log:
<Programs>
<Program Name="Trend Micro Worry-Free Business Security" Id="0006cad96a2e5505e5338e217885eedb0cd500000904" IconId="tmlisten.exe_88f9b1e96a75cfa0">
<CompatibilityInfo BlockingType="Hard" StatusDetail="UpgradeBlock"/>
<Link Target="https://go.microsoft.com/fwlink/?LinkId=2083777" Value="Weitere Informationen"/>
<Action Name="ManualUninstall" DisplayStyle="Text" ResolveState="NotRun"/>
</Program>
</Programs>
</CompatReport>
We will update Trend Micro today and try it again. Let see if it works.
Cheers - DeepM 3 years ago-
Glad you were able to find the cause. We've had a similar issue with our anti-virus in the past. - RyanTech 3 years ago
at the end of October, Windows 10 version 1803 represented 13.6% of 90,000 Windows 10 PCs it surveyed. The May 2019 Update, version 1903, rose 11% to 56.6%, making it the most widely adopted version of Windows 10. The Windows 10 October 2018 Update, version 1809, accounted for a quarter of all devices.
Top Answer
In this case was the problem an old Trend Micro Version.
Under C:\$WINDOWS.~BT\Sources\Panther\CompatData_2020_08_06_12_01_25_3_006f0018.xml you see which SW create the problem.
<Programs>
<Program Name="Trend Micro Worry-Free Business Security" Id="0006cad96a2e5505e5338e217885eedb0cd500000904" IconId="tmlisten.exe_88f9b1e96a75cfa0">
<CompatibilityInfo BlockingType="Hard" StatusDetail="UpgradeBlock"/>
<Link Target="https://go.microsoft.com/fwlink/?LinkId=2083777" Value="Weitere Informationen"/>
<Action Name="ManualUninstall" DisplayStyle="Text" ResolveState="NotRun"/>
</Program>
</Programs>
After updating all TM Agent Version ( https://downloadcenter.trendmicro.com/index.php?regs=nabu&clk=tbl&clkval=5276 ) we can now run the upgrade.
Cheers