Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs
Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs
Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
36 USMT_ERROR_UNSUPPORTED_PL<br />
ATFORM<br />
A store path can't be used because it contains<br />
data that could not be overwritten<br />
There was an error removing the store<br />
Compliance check failure; please check the<br />
logs for details<br />
Use of /offline is not supported during apply<br />
Use /offline to run gather on this platform<br />
37 USMT_ERROR_NO_INVALID_KEY The store holds encrypted data but the correct<br />
encryption key was not provided<br />
38 USMT_ERROR_CORRUPTED_NOTE An error occurred during store access<br />
NCRYPTED_STORE<br />
39 USMT_UNABLE_TO_READ_CONFIG<br />
_FILE<br />
40 USMT_ERROR_UNABLE_CREATE_P<br />
ROGRESS_LOG<br />
Error reading Config.xml<br />
File argument is invalid for /config<br />
Error writing to the progress log<br />
A migration store could not be<br />
deleted. If you are using a hardlink<br />
migration store you might have a<br />
locked file in it. You should<br />
manually delete the store, or use<br />
usmtutils /rd command to delete<br />
the store.<br />
Review ScanState log or LoadState<br />
log for details about command-line<br />
errors.<br />
Investigate whether there is an<br />
active temporary profile on the<br />
system.<br />
The /offline command was not<br />
used while running in the<br />
<strong>Windows</strong> Preinstallation<br />
Environment (<strong>Windows</strong> PE).<br />
The /offline command was not<br />
used while running in <strong>Windows</strong> PE.<br />
Verify that you have included the<br />
correct encryption /key or /keyfile.<br />
Review ScanState log or LoadState<br />
log for details about command-line<br />
errors. Make sure that the store<br />
path is accessible and that the<br />
proper permission levels are set.<br />
Review ScanState log or LoadState<br />
log for details about command-line<br />
errors in the Config.xml file.<br />
Check the command line you used<br />
to load the Config.xml file. You can<br />
use online Help by typing / on the<br />
command line.<br />
The Progress log could not be<br />
created. Verify that the location is<br />
Setup and<br />
Initialization<br />
Setup and<br />
Initialization<br />
Setup and<br />
Initialization<br />
Setup and<br />
Initialization<br />
Setup and<br />
Initialization<br />
Page | 47