After a successful P2V conversion, the VM fails to boot with 0xc0000225 The selected entry could not be loaded because the application is missing or corrupt. \windows\system32\winload.exe
|Article:TECH201230|||||Created: 2012-12-28|||||Updated: 2013-05-10|||||Article URL http://www.symantec.com/docs/TECH201230|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
After completing a successful Physical to Virtual conversion to a Vmware or Hyper-V host, the new virtual machine fails to boot with the error listed below.
0xc0000225 The selected entry could not be loaded because the application is missing or corrupt. \windows\system32\winload.exe
Backup Exec 2012
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
NOTE: Customers experiencing this issue are encouraged to contact Symantec Technical Support as data is still being collected to assist in resolving this issue.
AVVI: Unable to boot VM after P2V from physical machine.
Article URL http://www.symantec.com/docs/TECH201230