MDT Invalid credentials: The network was not found

MDT troubleshooting

The error message ‘Invalid credentials’ is shown when one of your platforms has trouble connecting due to the provided credentials being incorrect or permission errors. Here are some related errors you will come across when modifying Windows Image. How to fix error 0xc1510114: The wim file needs to be remounted, error 0x80070002: When trying to mount an image file, error code 15601: How to resolve DISM unspecified error when removing preinstalled packages, error 0xc1420127: The specified image in the specified wim is already mounted for read and write access, DISM Error 87: The package is unknown and Error 740: Elevated permissions are required to run DISM. What happens when WDS and DNS is installed on the same server: DNS issues with WDS. How to create a capture image on Windows Deployment Services, Windows Deployment Services: WDSUTIL CommandLine Options on Windows Server 2019.

Invalid network credentials

This error above was prompted because of permission issues associated with my Deployment Share and I also had to append the UserDomain to the bootstrap.ini. Here is the error below that was prompted.


To fix this, locate the Deployment Share and right-click on it
– Select Properties as shown below.

Network not found error

This will open the Deployment Share Properties Window as shown below.
– Click on the Security tab and
– Click on the Advanced button as shown below in order to set inheritance and take ownership of the share.

MDT authentication issues

This will open the Advanced Security for of the DeploymentShare

– Furthermore, Take ownership of the file and set the needed permission and
– Finally, click on “Replace all child object permission entries with inheritable permission entries from this object.

Next, we will have to edit the bootstrap.ini file in order to append the UserDomain to the bootstrap.ini
- To do open the Deployment Share file system.
- Click on the control folder and edit the bootstrap.ini file and
- Add "UserDomain=your domain here and save your file.

When you are done with the steps above, you will have to regenerate the Lite touch boot file again. To do this, follow the steps below. See this guide for more information about “ADK, MDT, and WDS: How to configure and deploy Windows using Microsoft Deployment Toolkit, and Windows Deployment Services for Windows 10“.

Right-click on the deployment share over the MDT and click on the “Update Deployment” share

After updating the Deployment Share folder, a LiteTouch WIM file will be created. These files will be located under the boot folder in the Deployment Share you created.

To Add the Lite-Touch Images to WDS, follow the steps below
– On the WDS-SERVER, open Windows Deployment Services (WDS),
– Right-click on the Boot Images and then
– Click on Add Boot Image, 

This still will go through the Lite Touch WinPE generation and when complete, you can replace the existing Lite Touch PE file on WDS. When next the client establishes a connection to the WDS server (PXE Server), the error will no longer be there and the installation will complete successfully as shown below.

For more on the configuration of MDT and WDS, see the following guides: ADK, MDT, and WDS: How to configure and deploy Windows using Microsoft Deployment Toolkit, and Windows Deployment Services for Windows 10. For WDS/DHCP scenarios: How to configure DHCP Server option 60, 66 and 67 for Windows Deployment Services, Uninstall WDS: How to remove Windows Deployment Services role via the GUI and PowerShell.

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Notify of

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x