Steps to Fix the “Invalid OS GUID” Error in MDT

Computer screen displaying steps to fix the 'Invalid OS GUID' error in Microsoft Deployment Toolkit (MDT) with 'Windows System Image Manager' open.

Deploying operating systems using Microsoft Deployment Toolkit (MDT) is straightforward until unexpected errors interrupt the process. One common issue you can encounter is the “Invalid OS GUID” error during task sequence execution. Therefore in this guide we will discuss the steps to Fix the “Invalid OS GUID” Error in MDT. Please see Faulting SecHealthUI: Resolve Windows Defender Notification, and how to Update Your AMD Radeon Display Adapter Driver.

Note: When MDT cannot resolve a valid OS GUID for the operating system package, the installation process loses track of its source files and fails completely.

Why “Invalid OS GUID” Causes Deployment Failure

The OS GUID is a unique identifier that MDT automatically assigns to each imported operating system in the Deployment Workbench. I think of it as a fingerprint for the specific Windows image to be deployed. As you can see from the smsts.log (bdd.log) below, we can see numerous entries with the “Error: Invalid OS GUID”. More on this as we progress through this guide.

If this GUID is missing, invalid, or mismatched, as it is in my case in MDT. MDT cannot locate the operating system files during the crucial “Install Operating System” step.

This will therefore result in the task sequence halting with errors like “Invalid OS GUID” logged behind the scenes. Below are some common Causes:

Incomplete Imports: The OS was not properly or fully imported into the Deployment Workbench (e.g., a corrupted WIM or ISO file transfer).
GUID Mismatch: The task sequence references a deleted, replaced, or heavily altered OS entry that no longer matches the original identifier.
Outdated Control Files: Offline media, Unattend.xml, or CustomSettings.ini were not properly updated after significant OS changes.

In my case, the issue was caused by an outdated control file. Although the correct operating system was selected and saved in the MDT Task Sequence, the Unattend.xml file was still configured to reference a different operating system from another deployment share. As a result, MDT attempted to deploy the wrong OS, leading to the error.

Please see how to update Proxmox VE to the latest version 9.2.3 today, Secure Boot 2023 Compliance Across WinPE, MDT, WDS, and ADK: Boot Chain Alignment and PXE Validation [Final Part], and how to Fix an error occurred while attempting to start selected VM on Hyper-V.

Identifying the Error in the Logs

When the deployment fails with the error “Invalid OS GUID”. We have to check the logs. As mentioned above, I have been able to determine indeed that the “Invalid OS GUID” is indeed the root cause. To determine this isse, please follow the steps below:

Navigate to your deployment logs folder (typically found under your network share or locally at C:\MININT\SMSOSD\OSDLOGS depending on the phase).
I analyzed both logs as shown below:
- BDD.log: The aggregated master log file for MDT execution.
- smsts.log: The primary log file for the Configuration Manager/MDT Task Sequence engine.
Open these logs using a text editor such as Notepad++ or CMTrace.

Next, use the search/find function to scan for the keyword “error” or “Invalid OS GUID”, as shown in the search workflow. You will likely see explicit error lines stating that the system failed to parse or find the specified GUID for the task sequence.

Please Failed to Upgrade VIHR Component: Failed to open deployer Service Management Port, The Backup Was Safe: The Data Center Was not: A Real-World Lesson About Hidden Data Center Risks and Governance Failures, and Enterprise Tape Library Administration: Control Path, Firmware, Media Management and Tape Operations.

Fixing the Invalid OS GUID in MDT

As mentioned earlier, the Task Sequence was already configured with the correct operating system image. However, the Unattend.xml file still contained a reference to a different operating system located in another deployment share. Because the referenced operating system no longer existed, MDT was unable to resolve the associated OS GUID, resulting in the “Invalid OS GUID” error.

Note: After confirming that the GUID reference was indeed broken, the resolution was straightforward: update the answer file so that it points to the correct operating system within the current deployment share.

Open your MDT Deployment Workbench.
Navigate to Deployment Shares and locate the affected deployment share.
Expand Task Sequences and open the properties of the affected Task Sequence.
Select the OS Info tab and verify that the correct operating system is selected.
Check the path configuration in the Windows System Image Manager (WSIM) / Answer File properties pane. If the path or the association is broken, you need to redirect it:
- Select the Install Operating System step in your task sequence.
- Re-link it to your currently imported Operating System image.
- Ensure that the Path field under the properties pane properly reflects the exact deployment share location of your operating system files (e.g., .\DeploymentShare\Operating Systems\...) as shown in the image below.

When done, save the updated Unattend.xml file and close WSIM and return to Deployment Workbench.

Please see How to Repair a Corrupt SQL Server Database Without Data Loss, Azure Application Gateway: Practical Configuration Guide, and Azure Managing Subscriptions with PowerShell: From Login-AzAccount to Resource Control and Private Endpoint Verification for Azure File Share”.

Update Deployment Share

Next, you need to right-click the deployment share and select Update Deployment Share. This will regenerate the boot images and replace existing boot media.