Running Sysprep caused Win7 VM to not boot!
-
Rockworthy
- Posts: 6
- Joined: 9. Sep 2010, 21:09
- Primary OS: MS Windows 7
- VBox Version: OSE Debian
- Guest OSses: Windows xp
Running Sysprep caused Win7 VM to not boot!
I'm just trying to use VirtualBox to create an installation of Windows 7 Home Premium that I can deploy on other, physical computers. I have run into a problem because when I run sysprep in the virtual machine, it runs okay, shuts down, and then it becomes unbootable! It gives a message about how there are no bootable devices detected or something similar. Anyone else run into this problem? I was thinking maybe this was because I installed Guest Additions...
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Running Sysprep caused Win7 VM to not boot!
No, the Guest Additions have nothing to do with booting: they basically consist of a replacement mouse and graphics drivers.
I have successfully used SysPrep in a VM in the past, and I can't think of anything VirtualBox could do to stop it working. On the other hand there is plenty that you could do.
The "No bootable devices found" means exactly what it says: the VM currently has no bootable disk attached to the VM. I doubt this has anything to do with SysPrep.
I have successfully used SysPrep in a VM in the past, and I can't think of anything VirtualBox could do to stop it working. On the other hand there is plenty that you could do.
The "No bootable devices found" means exactly what it says: the VM currently has no bootable disk attached to the VM. I doubt this has anything to do with SysPrep.