Winload.exe error, 0xc000000f
Posted: 11. Jun 2011, 07:11
Hi,
I hope this is not a repeat post. I search the forum briefly but did not found anything similar.
Just sharing a finding that puzzle me over the last couple of days.
I am currently using vpc 2007 and some of my vhd are sized 32GB while some are 64GB (Note: These are the reserved size. The actual usage are all around 13-16GB). They boot fine in vpc2007.
When I port them over to Virtual Box 4.0.8. Those that is 64GB all started to have winload.exe and 0xc000000f errors.
After trying to repair the winload.exe error without success. I tried the various settings in virtual box, PIIX3, PIIX4 etc... all still the same error.
Then I figure it could be due to the size of the vhd. So using the article from Heath Steward:
http://blogs.msdn.com/b/heaths/archive/ ... wsignin1.0
I reduce the 64GB to around 33GB. Then all these VHD are bootable again.
Hope this finding can help other people.
BTW, if anyone knows how to remove this limitation, do kindly share. Thanks in advance.
I hope this is not a repeat post. I search the forum briefly but did not found anything similar.
Just sharing a finding that puzzle me over the last couple of days.
I am currently using vpc 2007 and some of my vhd are sized 32GB while some are 64GB (Note: These are the reserved size. The actual usage are all around 13-16GB). They boot fine in vpc2007.
When I port them over to Virtual Box 4.0.8. Those that is 64GB all started to have winload.exe and 0xc000000f errors.
After trying to repair the winload.exe error without success. I tried the various settings in virtual box, PIIX3, PIIX4 etc... all still the same error.
Then I figure it could be due to the size of the vhd. So using the article from Heath Steward:
http://blogs.msdn.com/b/heaths/archive/ ... wsignin1.0
I reduce the 64GB to around 33GB. Then all these VHD are bootable again.
Hope this finding can help other people.
BTW, if anyone knows how to remove this limitation, do kindly share. Thanks in advance.