Thursday, June 4, 2026

Windows OS Logs Path

Hope you are doing well, 

Today I will be sharing details solutions while you are deploying MSI application and schedule deployment via MDM is not getting or want to troubleshoot and look details solutions or start finding fine tunes on where problem and what we have to look. This article will give you details study and logs path of the and what you have to look while having issue. Keep watching space @hiraniconfigmgr.com for more solution.

Let’s start for how to troubleshoot MSI deploy MDM applications.  

Windows OS Logs Path:

You can look here; settings > accounts > access work or school . Here you have the option to Export your management log files

c:\users\public\documents\MDMDiagnostics

Issue 1: The MSI Application does not appear in the Company Portal

Common Cause: MSI deployment over MDM is only available to Windows 10+ 

Issue 2: The MSI Job is not created

Things to check:

Did the Mobile MSI Job get delivered to the Client?

Check the registry for the following keys:

  • HKLM\SOFTWARE\Microsoft\EnterpriseDesktopManagement\S-0-0-00-0000000000-00000000000-00000000000-0000000000-00\MSI\<MSIProductID> (For Device targeted MSI Deployment).

  • HKLM\SOFTWARE\Microsoft\EnterpriseDesktopManagement\<UserSID>\MSI\<MSIProductID> (For User targeted MSI Deployments).

Issue 3: The application never installs

Things to check:

  1. Check the Statusand LastError registry values.

  2. Value definitions below:

  • 70 = Successfully installed/uninstalled

  • 10 = Initialized

  • 20 = DownloadInProgress

  • 25 = PendingDownloadRetry

  • 30 = DownloadFailed

  • 40 = DownloadCompleted

  • 48 = PendingUserSession

  • 50 = EnforcementInProgress

  • 55 = PendingEnforcementRetry

  • 60 = EnforcementFailed

  • 70 = EnforcementCompleted

Issue 4: Download Failure

Check the status of the BITS Job:

Run Bitsadmin /list /allusers 

Run Bitsadmin /info <BITSJobID> /verbrose.

Finally Check Logs:-

For Device targeted MSI deployments, logs will be written to %windows%\temp\<MSIProductID>.msi.log

For User targeted MSI Deployments, logs will be written to %temp%\MSIProductID.msi.log

Example: C:\users\Ian\AppData\Local\Temp\……..

That is about it, so once you work through these items you should have successfully deployed your MSI payload over the MDM channel.

Happy learining:-)

Thanks&regards,
Haresh Hirani
Email: [email protected], [email protected]
Facebook https://www.facebook.com/Hiraniconfigmgr-120189361980772/
Follow us: https://www.linkedin.com/in/hiraniconfigmgr 
Twitter: https://twitter.com/hiraniconfigmgr

Author

  • Hi, I’m Haresh Hirani the mind behind Hiraniconfigmgr.com. I’m a seasoned IT professional with deep expertise in Microsoft technologies, especially in Configuration Manager (ConfigMgr/SCCM). Over the years, I’ve expanded my skill set to cover a broader range of modern device management platforms like Microsoft Intune, Jamf Pro, ManageEngine Endpoint Central, and VMware AirWatch (Workspace ONE UEM), I use this blog to document real-world, tested, working fixes and walkthroughs from my daily technical experiences. The 💡idea is simple: if it helped me, it might help someone like you. My goal is to create a living repository of practical IT solutions for the community. If you find something useful, or if you want to collaborate, feel free to connect with me on LinkedIn or drop a message through the Contact page. Happy to help.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest posts