Search

Language:  

Available article translations:

Windows virtual machine starts with a Black screen

APPLIES TO:
  • Parallels Desktop 9 for Mac Standard Edition
  • Parallels Desktop 8 for Mac Standard Edition

Symptoms

Windows cannot start in any mode (neither normal no safe mode), all you see on the start is a black screen

Resolution

Corrupted or missing system file prevents Windows from booting normally.

Cause

Run System File Checker (sfc.exe) offline using two additional parameters, via the Windows Recovery Environment (Windows RE). Note: you will need Windows installation disk or .iso image.

1.Configure the virtual machine boot order such that the first boot device is your CD/DVD drive. - Without starting your virtual machine go to Virtual Machine menu ► choose Configure... ► select Hardware tab. - Highlight CD/DVD 1, make sure that Connected option is enabled and set Connect to to your physical CD/DVD drive (if you have an installation disk) or specify the path to corresponding .iso image.

Your text to link here...

  • Highlight Boot order ► on the right side of the window choose CD/DVD and using the up arrow move it to the first place.

Your text to link here...

2.If you use a Windows installation disk please insert it to CD-ROM, start your virtual machine.

Your text to link here...

3.When prompted, press a key to boot from the DVD. In the Install Windows screen, click Repair your computer.

Your text to link here...

4.Select TroubleshootAdvanced Options.

Your text to link here...

5.Click Command Prompt.

Your text to link here...

6.First use the command line to identify all drives attached to the system and their current mount point in Windows PE. This is done with the diskpart utility and the list volumes subcommand. C:\ is the boot volume (labeled "System Reserved") and D:\ is the system volume (where the operating system and user data are stored).

Your text to link here...

7.Run a chkdsk, this will verify/repair the filesystem and mark any bad sectors on the disk so that they are not used again.

Your text to link here...

8.Perform a sfc /scannow using the offline settings for the boot directory and windows directory. If you use the incorrect options, two errors are common:

    "Windows Resource Protection could not start the Repair service."

or

    "There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again."

The first error indicates an invalid boot or system partition path. The second indicates that incorrect arguments wre given, or there is a file that needs to be removed or renamed in the \Windows\winsxs\pending.xml path. For this installation, this is D:\Windows\winsxs\pending.xml.

For this particular system, this is the correct command to run based on the output of diskpart above

sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=d:\Windows

Your text to link here...

9.This process takes some time to complete. WindowsResourceProtection shouldfind corrupt files andrepaire them.Detailsare included inthe CBS.log

10.When it completes type ‘exit’ (without quotations) and restart your system.

11.Go to Virtual Machine menu ► choose Configure...Hardware tab ► highlight Boot Order and change the order back (make Hard disk to be the in first place).

12.If the system is still unbootable, it may be necessary to perform an in place upgrade or rescue the files and create a new virtual machine.




1e5db16426987d561060acdf56d947b4 a9c6e0b6a5209e617a7c0dd5eace86cf 97cd84747b25a2e5a06065a21a747a53 3307fff3682b15f0ba3fbe13d779296d

FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No