Issue: OSD.Upgrade.exe error during installation

Version 28

    Verified Product Versions

    Endpoint Manager 9.6Endpoint Manager 2016.xEndpoint Manager 2017.xEndpoint Manager 2018.x



    OSD.Upgrade.exe is run during the installation of an Ivanti EPM Service Pack or any Ivanti patch that updates the WinPE image (boot.wim). It is responsible for configuring the image to function on a specific Core Server and migrating WinPE drivers from the boot.wim.bak into the new boot.wim. If OSD.Upgrade.exe fails, one or more of these steps may not be completed. This document will walk through re-running the OSD.Upgrade.exe installation step on the core server.


    During the Service Pack or patch installation, there may be a failure with the OSD.Upgrade.exe process. The install error may be similar to CommonCore.inf: (0xFFFFFFFF) OSD.Upgrade.exe,60000.  Review the osd.upgrade.exe log file found in C:\Program Files (x86)\LANDESK\ManagementSuite\log to get more specific information about the error. If desired the osd.upgrade.exe.log file can be renamed prior to running osd.upgrade.exe again to make current errors easier to find.


    A common cause of this issue can be that one of the .WIM files is already mounted from a prior process or through manual intervention by an administrator.


    Common errors and description


    • Error: "Access Denied"

      • Errors referring to access denied indicates that a folder path in the boot.wim is too long. Often this path will be for a driver that was injected into the WinPE image. There are two option for correcting this error. The first option is to just start with a clean boot.wim and add the necessary drivers after completing the OSD.Upgrade.exe process. In LDMS 9 Service Pack 3 the WinPE boot environment requires Windows 7 32-bit drivers. Updating those drivers is a manual process so starting with a clean boot.wim may be a good option. The second option would be to mount the backup of the boot.wim (boot.wim.bak) and rename the directories in the InstalledDrivers directory to use shorter names. After completing one of these options follow the steps outlined below to re-run OSD.Upgrade.exe.

    • Error: "CommonCore.inf: (0xFFFFFFFF) OSD.Upgrade.exe,60000"

      • This is a general error indication. Review the log for additional errors.
      • Check to make sure the boot.wim is not mounted on the Core server.
        • The way to check this is running "dism /get-MountedWiminfo" from command prompt. This will show if wim's are mounted and where.
        • Check the OSD.Upgrade.exe.log file for any missing files. Then give it those missing files in the path that it is looking for them.
          • example: "09/06/2016 10:22:53 INFO  9680:1     RollingLog : File C:\Program Files\LANDesk\ManagementSuite\\ldlogon\provisioning\windows\Microsoft.VC90.CRT.manifest does not exist"
    • Error: "DirectoryNotFoundException"

      • Errors referring to a .0 or an mpkg package indicate that a .0 file has been extracted to a sub-folder of the ldlogon folder. DO NOT delete any .0 files from the root of ldlogon. Navigate to the directory specified in the log (i.e. C:\Program Files (x86)\LANDESK\ManagementSuite\ldlogon\mac) and delete the .0 file. To prevent additional errors when re-running OSD.Upgrade.exe delete any additional .0 files that are found in sub-folders of the ldlogon folder leaving only the .0 files in the root of ldlogon. Follow the steps below to re-run OSD.Upgrade.exe.
      • Errors referring an ALL.REG file indicate that the wim file was still mounted when osd.upgrade.exe tried to execute. This is most likely due to errors in the previous attempt at running OSD.Upgrade.exe. Review the log and correct and additional errors found before following the steps below to re-run OSD.Upgrade.exe.

    • Error: "Non-fatal error: FilterUnload failed, hr=0x801f0013"

      • This is normal and does not indicate a problem. Continue reviewing the log file for additional errors.

    • Error: "System.ComponentModel.Win32Exception"

      • You are running the process as a restricted user. Either log in as an administrative user or right click OSD.Upgrade.exe and select run as administrator.
        • Make sure that you are either logged directly into the core server or using Remote Desktop with a /admin switch as a full administrator.

    • Error: "System.IO.IOException: Element not found"

      • This error indicates that there is still a wim file mounted. Review the log for additional errors prior to this error. Follow steps below to re-run the OSD.Upgrade.exe process.

    • Error: "System.UnauthorizedAccessException"

      • This error indicates either that there is still a wim file mounted, or that the bootmedia.wim.bak already exists. Bootmedia.wim.bak can be deleted as long as bootmedia.wim exists. Review the log for additional errors and then follow the step below to re-run OSD.Upgrade.exe.

    • Error: "WAIK is not installed"

      • This is normal and does not indicate a problem. WAIK should have been uninstalled prior to upgrade. If WAIK is installed, uninstall it. Continue reviewing the log file for additional errors.

    • Error: "CommonCore.inf: (0xFFFFFFFF) OSD.Upgrade.exe,90000"

      • Download Streams from Microsoft ( Go into properties of Streams an unblock the application. Run Streams against the folder the Ivanti EPM installer was xtraced to and run Streams against the folder LANDESK is being installed to (ie, \Program Files\LANDESK). Make sure the Ivanit EPM installer is being run locally (not networked drive), you are upgrading the machine locally (not RDP) and run the installer as Administrator.


    • Issue: Upgrade fails at HII step

      • Log will display RollingLog : HII: Setting driver repository path to "\\LDCoreName\ldmain\landesk\files\drivers" 08/05/2015 12:03:10 INFO 8732:1 RollingLog : HII: Initial driver file count to process:
      • In the \\LDCoreName\ldmain\landesk\files\drivers directory will be a db3 and db3 bak file. Rename the file to db3.old and db3 bak.old. Quit out of the installer and re-open and start install again

    Preparing to Re-Run OSD.Upgrade.exe

    After reviewing your errors and completing the steps above perform the following steps:


    1. Start an administrator command prompt (right click the command prompt and select run as administrator).
    2. From the command prompt navigate to C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot.
    3. Run the following command:

      DISM.EXE /Get-MountedWimInfo
      • The command should list all images that are currently mounted. There are instances however where a mounted image will not be listed. Check for the existence of the folder original_boot_wim and/or new_boot_wim in the C:\Users\logged in user \AppData\Local\Temp\imgtmp\ directory.

    4. For each image listed and all folders found in the imgtmp directory listed in step 1, run the following commands:

      • DISM.EXE /Unmount-Wim /mountdir:"c:\path to dir(s) found in previous step" /discard  Where mountdir is the mount path listed from the dism.exe /Get-MountedWimInfo command or the folders specified in step 3.
      • DISM.EXE /Cleanup-Wim
      • Ensure that each unmount command completes successfully
      • Any errors that DISM may encounter will be logged in the %windir%\Logs\DISM directory.  (For further information see Understanding Failures and Log Files)
    5. In Windows Explorer open the C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot directory.
    6. Rename the existing boot.wim to boot.wim.bad.
    7. Copy the backup boot.wim (the one from prior to upgrading) from C:\Program Files (x86)\LANDesk\ManagementSuite\backup\PatchName\ to the C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot directory.
      • If access denied errors occurred with drivers and a clean boot.wim file is desired, use the file listed in step 9 below.
    8. Rename the restored boot.wim file in the vboot directory to boot.wim.bak.
    9. Copy the boot.wim file from the installation package \image directory to the \vboot directory. You should now have a boot.wim and boot.wim.bak (either your backup or an additional copy from the patch) file in the vboot directory.
    10. Run the OSD.Upgrade.exe from C:\Program Files (x86)\LANDesk\ManagementSuite\. This should take a few minutes to complete. If it exits quickly it is likely that there are additional errors.
    11. Review the OSD.Upgrade.exe log found in C:\Program Files (x86)\LANDesk\ManagementSuite\logs to see if any additional errors were encountered. If additional errors were encountered, you must resolve each one and after resolving re-run OSD.Upgrade.exe.
    12. If this still does not resolve the issue check "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" and remove any values in the key.


    After OSD.Upgrade.exe has completed successfully you need to redeploy your PXE reps. Instructions for PXE deployment can be found at How to deploy PXE Representatives(step-by-step screenshots)


    When a client machine boots into WinPE open a console to confirm the upgrade. The version shown in the console should be 6.1.7601 or higher.