mdt
15 TopicsMoving from MDT/WDS to Autopilot – Real-World Lessons, Wins & Gotchas
Hi all, We’ve been moving away from an ageing WDS + MDT setup and over to Windows Autopilot, and I thought I’d share a few key lessons and experiences from the journey. In case anyone else is working through the same transition (...or about to). Why the change? MDT was becoming unreliable, drivers/apps would randomly fail to install, WDS is on the way out, and we needed a more remote-friendly approach. We also wanted to simplify things for our small IT team and shift from Hybrid Azure AD Join to Azure AD Join only. We’re doing this as a phased rollout. I harvested existing device hashes using a script from a central server, and manually added machines that weren’t online at the time (most of which were just unused spares, we haven't introduced new hardware yet). If you want a copy of this auto-harvest, please see my next post, this script is useful as it'll just go off and import the hardware hashes into Intune, and can run against multiple computers at a time. (I will add the link to the post once made). Some of the biggest hurdles: • 0x80070002 / 0x80070643 errors (typically due to incomplete registration or app deployment failures) • Enrollment Status Page (ESP) hangs due to app targeting issues (user vs device) and BitLocker config conflicts • Wi-Fi setup with RADIUS (NPS) was complex, Enterprise Certificates and we're still using internal AD for authentication, so user accounts exist there and sync over to Azure. • Legacy GPOs had to be rebuilt manually in Intune, lots of trial and error • Some software (like SolidWorks) wouldn’t install silently via Intune, so I used NinjaOne to handle these, along with remediation scripts in Intune where needed We also moved from WSUS to Windows Autopatch, which improved update reliability and even helped with driver delivery via Windows Update. What’s gone well: Device provisioning is more consistent, updates are more reliable, build time per machine has dropped, and remote users get systems faster. It’s also reduced our reliance on legacy infrastructure. What I’m still working on: Tightening up compliance and reporting, improving detection/remediation coverage, figuring out new errors that may occur, and automating as much manual processes as possible. Ask me anything or share your own experience! I’m happy to help anyone dealing with similar issues or just curious about the move. Feel free to reply here or message me. Always happy to trade lessons learned, especially if you’re in the middle of an Autopilot project yourself. Cheers, Timothy Jeens459Views3likes5CommentsMoving from MDT/WDS to Autopilot part 2
Hi everyone Following up on my previous post about moving from MDT/WDS to Windows Autopilot, I wanted to share some of the more detailed parts of the deployment and config that might help others working through similar issues. Wi-Fi (RADIUS + NPS + Azure AD Join): This was hands-down one of the trickiest bits. We use a local RADIUS server (Windows NPS) with certificates for EAP authentication, and users authenticate using local AD credentials, despite Autopilot devices being Azure AD joined. I had to build a custom Wi-Fi configuration profile in Intune that handled certificate trust, proper targeting, and worked with our existing NPS policies. If anyone needs help with this scenario, I’m happy to share more details. I’ll be posting the full configuration soon. BitLocker Conflicts: BitLocker generally worked but only after cleaning up overlapping configurations. Intune allows BitLocker settings to be applied via multiple paths (Device Configuration, Endpoint Security, Encryption, even legacy GPOs via ADMX). I found they MUST be aligned across all sources — otherwise, ESP fails or encryption doesn’t trigger. My fix: consolidate BitLocker settings under Endpoint Security and Windows Configurations and ensure nothing else contradicts them, they give different options hence the need for the two. App Deployment + Detection Scripts: Some software just doesn’t play nice with Intune alone. We had issues with SolidWorks and other legacy tools. For these, I used NinjaOne to run custom silent installers and Intune detection scripts to track success and reapply if needed. For complex installs, I had to fall back on Proactive Remediation scripts to detect and fix problems. Compliance Baselines & Settings: We're gradually shifting to Intune-based compliance. I ported over our core GPO baselines and rebuilt them using Configuration Profiles, Settings Catalog, and Security Baselines. Compliance policies then reference these, so non-conformant machines are flagged. Still evolving this as we onboard more devices. Licensing Requirements: For anyone wondering, some of these capabilities require specific licensing. We're running "Microsoft 365 E3" + "Enterprise Mobility + Security E3", which gives us access to: Proactive Remediations Intune-based compliance management Scripted deployments and reporting Note, only 1 user in the tenant needs these two licences to enable the features. Summary This move to Autopilot wasn’t just a deployment change, it pushed us to rethink how we handle security, authentication, app installs, and policy enforcement. There’s still more to do, but we’ve built a solid foundation that’s scalable and more resilient than our old MDT-based approach. If you’re dealing with similar challenges or stuck on something like Wi-Fi, BitLocker or app installs, feel free to reach out. I’ve probably hit the same wall and am happy to compare notes or share scripts/settings if it helps. Cheers, Timothy Jeens74Views0likes0CommentsMDT - Getting LapsAdmin User - Apps not getting installed
Hi, Thank you in advance for your help. If I don't join the computer to the domain, it uses local Administrator account and installs all the apps (office, adobe, etc.) correctly. Once I use the domain settings (highlighted below) it will join the domain, boots up into login screen using "LAPSAdmin" user displays "password incorrect" error, and none of the apps get installed. Thoughts? (TY) ---------------------------------------------------------------- [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipCapture=YES SkipAdminPassword=YES SkipProductKey=YES SkipComputerBackup=YES SkipBitLocker=YES ;SkipComputerName=YES OSDComputerName=MDT-%SerialNumber% ;SkipDomainMembership=YES ;JoinDomain=domain.xyz.com ;DomainAdmin=admin ;DomainAdminPassword=password1 ;DomainAdminDomain=domain.xyz.com SkipUserData=YES UserDataLocation=NONE ;SkipLocaleSelection=YES InputLocale=0409:00000409 SystemLocale=en-US UILanguage=en-US UserLocale=en-US SkipTimeZone=YES TimeZoneName=Eastern Standard Time ;SkipAdminPassword=YES AdminPassword=LocalAdmin!79Views0likes1CommentDeployment Win11 on OEM Licence
Hello, does anyone know which Licence i need for Installing an Win 11 iso and Deploy it with MDT / WDS Creating is Free i think. The Pcs we buy have an installed Win 11 Pro for example Lenovo ThinkCentre so they have an OEM Version of Win 11 and i want to Deploy our own Win 11 Pro with Pre Installed Software. Is this included in the Win 11 Pro Version or do i need Win 11 SA or a System Builder Licence? Do i just need one Licence or for each Device one? i hope someone can help me with this Question.158Views0likes1CommentMDT and GPO Pack
Hello la commune 🙂 While reading thouroughly the MDT Doc (https://learn.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/get-started-with-the-microsoft-deployment-toolkit), I noticed that it mentionned that MDT suuports applying GPO Packs using Windows SCM, but according to this (Security Compliance Manager (SCM) retired; new tools and procedures - Microsoft Community Hub) it was retired and a new solution was introduced to replace it, that's Security Compliance Toolkit (SCT). So, can one still use SCM for applying GPO Pack while deploying using MDT, or should we absolutely go with SCT? If yes, what should be done to correct the Doc, because as you can see, it's misleading Thank you la commune955Views0likes0CommentsWhich ADK version to deploy Win 10 Pro 22H2 from a Win2022 server?
Hello community, I'm confused about the use of ADKs. I'm trying to deploy Windows 10 pro 22H2 from an MDT server 2022. The ADKs ... 2022, 2004 refuse to install and I have catalog generation problems with versions 11. Is it I possible to deploy Win10_Pro from a 2022 server? Thank you for your help.592Views0likes0CommentsChecking the connection to Microsoft. This might take a while.
I have WDS and MDT configured to deploy windows 10 to Lenovo ThinkPad 15 Gen2 along with network driver and all the things needed. Due to a minor misconfiguration right network drivers were not being injected. But when we are doing the same windows 10 installation through Bootable USB, we won't be including any drivers in that, but that still works. What I don't understand is the whole WDS deployment happens on the private network which doesn't need internet which I am being mandated for the process after MDT GUI has done its work the laptop restarts and saying "Checking the connection to Microsoft. This might take a while." as the landing page and getting stuck there for hours not letting me go any further. Please help me understand the part where it says it is trying to connect to Microsoft and getting stuck meaning it is trying to connect to internet when there is no need for that.729Views0likes1CommentMicrosoft Patching is not working until User logon to the newly imaged device
Hi All, I have a customer that they have two separate SCCM and WSUS environments in the same domain and they use SCCM for OS imaging and WSUS for patch updates. The problem is end user hast to logon to the device after imaging the OS using SCCM to kick start the patching process from WSUS. My client's understanding is that it should work without user logon to the device since GPO targeted to all authenticated users. Please also note that the computer objects and other settings are working without any issues. I would appreciate if anyone come across such a behavior and there is any workaround that we can do kick start the patching regardless of user login or is this behavior by design? Thanks, Dilan590Views0likes0CommentsMDT - Packages added but "nothing to save"
**Logs listed below main post** I am attempting to add ja-JP Language Pack and Features via the Packages section in MDT (Version: 6.3.8456.1000). ZTIPatches.log finds the packages and cites they are being added, but then the next line notes "Nothing to save, exit." implying that the packages were not added. No other lines appear to show error. Viewing the DISM logs, these packages do not show at all either. Checking the installed packages post deploy obviously shows these packages are not installed. Architecture matches (amd64) and they are the latest available for my target build (2004 lp and fod, target build 21h2), imported in to MDT Packages direct from the appropriate ISOs from vlpc. Can anyone illuminate what may (not) be happening? **ZTIPatches.log** <![LOG[Microsoft Deployment Toolkit version: 6.3.8456.1000]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[ZTIPatches Entered POSTINSTALL state. Deployment Method = UNC]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Operating system being deployed requires amd64 updates.]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Load XML....]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Adding non-language pack entries to unattend.xml]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[ Open Control File: Packages]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Found 5 matching non-language pack entries.]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[An empty <servicing> node was found, removing and recreating.]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Add package {93451c97-476d-4cc9-8d20-4bdd28e145e4}]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Add package {0162c317-78ab-4cf4-8d8c-6ea2a422b4c1}]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Add package {80a9e949-0083-4d4d-b747-b2917f0dd393}]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Add package {f6a1dfe4-44de-4c85-815a-d8831aec9dae}]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Add package {21042c1b-27de-41f4-8283-7c9e0e2b7921}]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Nothing to save, exit.]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Adding language pack entries to unattend.xml]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[An empty <servicing> node was found, removing and recreating.]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Add package {7e493b46-9ec2-4b3d-845b-381f15ad73b7}]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Nothing to save, exit.]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Language pack entries added to unattend.xml successfully]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[ZTIPatches processing completed successfully.]LOG]!><time="16:14:43.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> <![LOG[Event 41001 sent: ZTIPatches processing completed successfully.]LOG]!><time="16:14:44.000+000" date="09-16-2022" component="ZTIPatches" context="" type="1" thread="" file="ZTIPatches"> **DISM.log** 2022-09-16 16:27:30, Info DISM PID=1812 TID=1524 Scratch directory set to 'C:\Users\ADMINI~1\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir 2022-09-16 16:27:30, Info DISM PID=1812 TID=1524 DismCore.dll version: 10.0.19041.746 - CDISMManager::FinalConstruct 2022-09-16 16:27:30, Info DISM Initialized Panther logging at C:\windows\Logs\DISM\dism.log 2022-09-16 16:27:30, Info DISM PID=1812 TID=1524 Successfully loaded the ImageSession at "C:\windows\system32\Dism" - CDISMManager::LoadLocalImageSession 2022-09-16 16:27:30, Info DISM Initialized Panther logging at C:\windows\Logs\DISM\dism.log 2022-09-16 16:27:30, Info DISM DISM Provider Store: PID=1812 TID=1524 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2022-09-16 16:27:30, Info DISM DISM Provider Store: PID=1812 TID=1524 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect 2022-09-16 16:27:30, Info DISM DISM Provider Store: PID=1812 TID=1524 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect 2022-09-16 16:27:30, Info DISM Initialized Panther logging at C:\windows\Logs\DISM\dism.log 2022-09-16 16:27:30, Info DISM DISM Manager: PID=1812 TID=1524 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession 2022-09-16 16:27:30, Info DISM DISM.EXE: 2022-09-16 16:27:30, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2022-09-16 16:27:30, Info DISM DISM.EXE: 2022-09-16 16:27:30, Info DISM DISM.EXE: Host machine information: OS Version=10.0.19044, Running architecture=amd64, Number of processors=2 2022-09-16 16:27:30, Info DISM DISM.EXE: Dism.exe version: 10.0.19041.844 2022-09-16 16:27:30, Info DISM DISM.EXE: Executing command line: "C:\windows\system32\Dism.exe" /online /get-packages 2022-09-16 16:27:30, Info DISM DISM Provider Store: PID=1812 TID=1524 Connecting to the provider located at C:\windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:30, Info DISM DISM Manager: PID=1812 TID=1524 physical location path: C:\ - CDISMManager::CreateImageSession 2022-09-16 16:27:30, Info DISM DISM Manager: PID=1812 TID=1524 Event name for current DISM session is Global\{9069F4E8-36EB-4C61-A37F-749CF1AAC947} - CDISMManager::CheckSessionAndLock 2022-09-16 16:27:30, Info DISM DISM Manager: PID=1812 TID=1524 Create session event 0x21c for current DISM session and event name is Global\{9069F4E8-36EB-4C61-A37F-749CF1AAC947} - CDISMManager::CheckSessionAndLock 2022-09-16 16:27:30, Info DISM DISM Manager: PID=1812 TID=1524 Copying DISM from "C:\windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation 2022-09-16 16:27:32, Info DISM DISM Manager: PID=1812 TID=1524 Successfully loaded the ImageSession at "C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA" - CDISMManager::LoadRemoteImageSession 2022-09-16 16:27:32, Info DISM DISM Image Session: PID=7432 TID=3260 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore 2022-09-16 16:27:32, Info DISM DISM Provider Store: PID=7432 TID=3260 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect 2022-09-16 16:27:32, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:32, Info DISM DISM OS Provider: PID=7432 TID=3260 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect 2022-09-16 16:27:32, Info DISM DISM OS Provider: PID=7432 TID=3260 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect 2022-09-16 16:27:32, Info DISM DISM Provider Store: PID=7432 TID=3260 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect 2022-09-16 16:27:32, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:32, Info DISM Initialized Panther logging at C:\windows\Logs\DISM\dism.log 2022-09-16 16:27:32, Info DISM DISM Provider Store: PID=7432 TID=3260 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2022-09-16 16:27:32, Warning DISM DISM Provider Store: PID=7432 TID=3260 Failed to load the provider: C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2022-09-16 16:27:32, Info DISM DISM Provider Store: PID=7432 TID=3260 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect 2022-09-16 16:27:32, Info DISM DISM Provider Store: PID=7432 TID=3260 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect 2022-09-16 16:27:32, Info DISM Initialized Panther logging at C:\windows\Logs\DISM\dism.log 2022-09-16 16:27:32, Info DISM Initialized Panther logging at C:\windows\Logs\DISM\dism.log 2022-09-16 16:27:32, Info DISM DISM Manager: PID=1812 TID=1524 Image session successfully loaded from the temporary location: C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA - CDISMManager::CreateImageSession 2022-09-16 16:27:32, Info DISM DISM.EXE: Target image information: OS Version=10.0.19044.1889, Image architecture=amd64 2022-09-16 16:27:32, Info DISM DISM.EXE: Image session version: 10.0.19041.746 2022-09-16 16:27:32, Info DISM DISM Provider Store: PID=7432 TID=3260 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection 2022-09-16 16:27:32, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:32, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:32, Info CSI 00000001 Shim considered [l:126]'\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 2022-09-16 16:27:32, Info CSI 00000002 Shim considered [l:123]'\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll' : got STATUS_SUCCESS 2022-09-16 16:27:33, Info DISM DISM OS Provider: PID=7432 TID=3260 Determined System directory to be C:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory 2022-09-16 16:27:33, Info DISM DISM Package Manager: PID=7432 TID=3260 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize 2022-09-16 16:27:33, Info CSI 00000001 Shim considered [l:126]'\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 2022-09-16 16:27:33, Info CSI 00000002 Shim considered [l:123]'\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll' : got STATUS_SUCCESS 2022-09-16 16:27:33, Info DISM DISM Package Manager: PID=7432 TID=3260 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize 2022-09-16 16:27:33, Info DISM DISM Package Manager: PID=7432 TID=3260 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info CSI 00000001 Shim considered [l:126]'\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 2022-09-16 16:27:33, Info CSI 00000002 Shim considered [l:123]'\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll' : got STATUS_SUCCESS 2022-09-16 16:27:33, Info DISM DISM Driver Manager: PID=7432 TID=3260 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Warning DISM DISM Provider Store: PID=7432 TID=3260 Failed to load the provider: C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\SysprepProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Transmog Provider: PID=7432 TID=3260 Current image session is [ONLINE] - CTransmogManager::GetMode 2022-09-16 16:27:33, Info DISM DISM Transmog Provider: PID=7432 TID=3260 Audit Mode: [No] - CTransmogManager::Initialize 2022-09-16 16:27:33, Info DISM DISM Transmog Provider: PID=7432 TID=3260 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType 2022-09-16 16:27:33, Info DISM DISM Transmog Provider: PID=7432 TID=3260 Product Type: [WinNT] - CTransmogManager::Initialize 2022-09-16 16:27:33, Info DISM DISM Transmog Provider: PID=7432 TID=3260 Product Type ServerNT : [No] - CTransmogManager::Initialize 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\C330E5BB-AF4B-40E2-9749-4E50C3422CAA\SetupPlatformProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM Provider Store: PID=7432 TID=3260 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2022-09-16 16:27:33, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: IBSManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: AppxManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: AppxManager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: ProvManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: ProvManager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: AssocManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: AssocManager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericManager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: SysprepManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: SysprepManager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager. 2022-09-16 16:27:33, Info DISM DISM.EXE: Attempting to add the commands from provider: SetupPlatformManager 2022-09-16 16:27:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: SetupPlatformManager. 2022-09-16 16:27:33, Info DISM DISM Package Manager: PID=7432 TID=3260 Processing the top level command token(get-packages). - CPackageManagerCLIHandler::Private_ValidateCmdLine 2022-09-16 16:27:33, Info DISM DISM Package Manager: PID=7432 TID=3260 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine 2022-09-16 16:27:33, Info DISM DISM Package Manager: PID=7432 TID=3260 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-OneCore-ApplicationModel-Sync-Desktop-FOD-Package~31bf3856ad364e35~amd64~~10.0.19041.1503 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-OneCore-DirectX-Database-FOD-Package~31bf3856ad364e35~amd64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1889 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-FodMetadata-Package~31bf3856ad364e35~amd64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Hello-Face-Migration-Package~31bf3856ad364e35~amd64~~10.0.19041.1889 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Hello-Face-Package~31bf3856ad364e35~amd64~~10.0.19041.1889 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~11.0.19041.1566 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-LanguageFeatures-Speech-en-us-Package~31bf3856ad364e35~amd64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package~31bf3856ad364e35~amd64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~10.0.19041.1889 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-MSPaint-FoD-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-MSPaint-FoD-Package~31bf3856ad364e35~amd64~~10.0.19041.746 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-MSPaint-FoD-Package~31bf3856ad364e35~wow64~en-US~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-MSPaint-FoD-Package~31bf3856ad364e35~wow64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.488 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~amd64~~10.0.19041.1865 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~wow64~en-US~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~wow64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~amd64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~wow64~en-US~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~wow64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Printing-PMCPPC-FoD-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Printing-PMCPPC-FoD-Package~31bf3856ad364e35~amd64~~10.0.19041.1806 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Printing-WFS-FoD-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.906 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-Printing-WFS-FoD-Package~31bf3856ad364e35~amd64~~10.0.19041.1889 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-QuickAssist-Package~31bf3856ad364e35~amd64~~10.0.19041.1566 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-StepsRecorder-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-StepsRecorder-Package~31bf3856ad364e35~amd64~~10.0.19041.746 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-StepsRecorder-Package~31bf3856ad364e35~wow64~en-US~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-StepsRecorder-Package~31bf3856ad364e35~wow64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-TabletPCMath-Package~31bf3856ad364e35~amd64~~10.0.19041.1865 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-UserExperience-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.1741 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-WordPad-FoD-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-WordPad-FoD-Package~31bf3856ad364e35~amd64~~10.0.19041.1682 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-WordPad-FoD-Package~31bf3856ad364e35~wow64~en-US~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Microsoft-Windows-WordPad-FoD-Package~31bf3856ad364e35~wow64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package OpenSSH-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.964 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4510.2 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Package_for_KB5003791~31bf3856ad364e35~amd64~~19041.1237.1.3 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1889.1.16 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Package_for_ServicingStack_1704~31bf3856ad364e35~amd64~~19041.1704.1.4 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Package Package_for_ServicingStack_1852~31bf3856ad364e35~amd64~~19041.1852.1.0 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Package Manager: PID=7432 TID=3260 Finalizing CBS core. - CDISMPackageManager::Finalize 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(SysprepManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: SysprepManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Finalizing the servicing provider(SetupPlatformManager) - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: SetupPlatformManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=7432 TID=3260 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Manager: PID=1812 TID=1524 Closing session event handle 0x21c - CDISMManager::CleanupImageSessionEntry 2022-09-16 16:27:34, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2022-09-16 16:27:34, Info DISM DISM.EXE: 2022-09-16 16:27:34, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2022-09-16 16:27:34, Info DISM DISM.EXE: 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=1812 TID=1524 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=1812 TID=1524 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 16:27:34, Info DISM DISM Provider Store: PID=1812 TID=1524 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider 2022-09-16 18:35:30, Info DISM PID=5132 TID=4508 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct 2022-09-16 18:35:30, Info DISM PID=5132 TID=4508 Scratch directory set to 'C:\windows\TEMP\'. - CDISMManager::put_ScratchDir 2022-09-16 18:35:30, Info DISM PID=5132 TID=4508 DismCore.dll version: 10.0.19041.746 - CDISMManager::FinalConstruct 2022-09-16 18:35:30, Info DISM PID=5132 TID=4508 Scratch directory set to 'C:\$WinREAgent\Scratch'. - CDISMManager::put_ScratchDir 2022-09-16 18:35:30, Info DISM Initialized Panther logging at C:\windows\Logs\DISM\dism.log930Views0likes0Comments