[Solved] installing W7-x64 failed

[gabriello]

installing W7-x64 failed

Postby gabriello » 1. Jan 2019, 17:01
Hello:
I bought a new laptop with W10 pre-installed, I installed VirtualBox 5.2.18 and tried to install W7-x64 ( because many programs don't run on W10), I put the W7 CD and began to create a new machine, after while installation stopped with black screen with the following message:

Windows Boot Manager
windows failed to start. A recent hardware or software change might be the
cause. To fix the problem:
1. insert your windows installation disc and restart your computer.
2. choose your language settings, and then click "Next."
3. click "Repair your computer."
if you do not have this disc, contact your system administrator or computer manufacturer for assistance.
Fi1e: \windows\system32\boot\winload.exe
Status: 0xc000035a
info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode.

any help is greatly appreciated, I need W7 absolutely

Thanks in advance

laptop model: hp 17z-ak000
processor AMD A12-9720p

[gabriello]

In fact, checking back Virtual Box, I noticed that in "Configuration" --> general -->basic --> version, there is no option for 64 bits systems.
are 64 bits systems not supported?

using version 5.2.18

[mpack]

FAQ: I have a 64bit host, but can't install 64bit guests.

[gabriello]

Thanks for reply
I checked my laptop, my CPU AMD A12-9720p supports virtualisation, I enabled it in BIOS (it was disabled), then I re-lauched VirtualBox and tried to setup W7-x64 machine, it started reading from the setup dvd, then black screen with this message:

windows failed to start. A recent hardware or software change might be the cause. To fix the problem:

1. insert your windows installation disc and restart your computer.
2. choose your language settings, and then click "Next."
3. Click "Repair your computer."

if you do not have this disc, contact your system administrator or computer manufacturer for assistance.
Status: 0xc0000225
info: An unexpected error has occurred

any hint?

thank you

[socratis]

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[gabriello]

here it is

[andyp73]

00:00:03.861730   VRamSize         <integer> = 0x0000000001500000 (22 020 096, 21 MB)

You might want to push this up to 64MB or 128MB.

00:01:22.073870 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=16 \Device\HarddiskVolume3\Program Files\ShellFolderFix\ShellFolderFix.dll
00:01:22.074075 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\ShellFolderFix\ShellFolderFix.dll' (C:\Program Files\ShellFolderFix\ShellFolderFix.dll): rcNt=0xc0000190

The Shell Folder Fix utility that you are using appears not to have properly signed DLLs and these are trying to get into the VirtualBox memory space. If you can't tell it to leave VirtualBox alone then you may need to uninstall it.

-Andy.

[gabriello]

I've uninstalled ShellFolderFix and put Video RAM to 128MB, the problem remains the same.
I'm attaching the log file

[mpack]

It's actually the VBoxHardening.log that we need to diagnose hardening problems.

This time, please do not forget to zip the log.

[gabriello]

here it is

[mpack]

No hardening error is reported in the log. So, back to the VM.

Are you quite sure that the guest OS is Win7-64bit? Some of the symptoms you mention can happen if you (say) tried to install Win8.1 using a Win7 template.

I am also not seeing the problem you mention of not being able to select a 64bit template: the current template is 64bit.

Incidentally, you should set the number of CPUs to 2, Win7 will not run so well with one core. Also I'd double the RAM to 2GB.

I'd like to eliminate potential problems with the host DVD drive. I would suggest imaging the DVD to an ISO, and mounting the ISO in the virtual drive instead of linking it to a host drive.

[gabriello]

I've set the number of CPU to 2 and RAM to 2GB, Finally it worked!!! thank you

I still have another problem: in configuration, I added drive E: as shared folder, I don't see it in "My computer" windows explorer.

is there any trick?

thank you

[mpack]

I'm not sure you can call it a trick, but shared folders can be found in the network neighborhood (vboxsvr) branch of explorer.

[gabriello]

I checked again and again, I don't see my shared partition e:\ nowhere, can this be related to the type of my hard disk being "gpt" and not "mbr"?
In my other "xp" machine everything is ok, I see shared partitions normally.

thanks in advance

[Peter15NTl]

I don't see my shared partition e:\ nowhere,...

Hi, gabriello!
You may have disabled network file access. This can be checked in the Network Management Center. What happens if you click on the "network" on the left side of the "My Computer" window?