This error is caused when the working directory no longer exists that is assigned to the application being installed. It would be nice if MDT published which app it is, but it does not. To find the application, open up the BDD.LOG file. Search for the error message. You will see the directory it is trying to access on the line above. Just a few lines above, it should also display the app the directory is associated with right above the ################ line .
Awards & Accolades
Popular Posts
-
The firm I am at has recently upgraded all systems to the newest model Dells. In doing so, some of the settings for configuring WOL have cha... -
Here is a script that will activate both Microsoft Office and Microsoft Windows. I wrote this script because we currently have both x86 a... -
Font installation using PowerShell has changed since Windows 10 1909. The old way of doing it with PowerShell no longer works. This new scri...
-
You are installing RSAT in a build, and you want to check if it is installed if it is included in the windows updates. Recently, there has...
-
If you have a system that has been infected or the drive had to be replaced, you'll need to lay down a new bare OS and then have autopil... -
Recently, we wanted to start keeping track of users with mapped drives due to cryptolocker vulnerabilities. There are a few applications w... -
When you open registry editor and connect to a remote system, the only hives you will see are HKEY_LOCAL_MACHINE and HKEY_USERS. The other ...
-
I was deploying a package earlier today. It took a few iterations to get everything correct. All of a sudden on the fourth update of the pa...
-
Unlike what most blogs are saying that you need to extract the AdobePDF.dll from the data1.cab file, which is one option, there is a m... -
Recently, we needed a report of the last boot time of all servers. I wrote this PowerShell script that queries AD for a list of all windows ...
0 comments:
Post a Comment