top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Upgrade win7 running under VirtualBox to Win10 fails?

+1 vote
322 views

I'm running win7 prof under Fedora/VirtualBox-5.0-5.0.10_104061_fedora22-1.x86_64 with a valid product key.

If I try to upgrade to win10, it's rejected: cpu not supported (or similar), and not supported video card (the last seems to be a minor issue).

But my CPU is: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz. The NX bit is on.

Installing win10 by the media creation tool in VirtualBox runs flawlessly (only the product key is invalid).

So my question: Anybody made similar experiences and could solve the issue?

posted Nov 16, 2015 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
0 votes

FSL in VMware workstation play on windows 10. I am not able to open 80 MB or its compressed form 27 Mb file of .nii extension while 18Mb file is opening in FSLeyes.

0 votes

I am using Virtualbox on a Windows 10 host system, a Fedora 25 guest system, and with guest additions.

I recently had a Windows 10 automatic update and this problem did not seem to occur before that. I have tried to uninstall the updates, but I think some of the changes are left behind.

The crash seems to happen while I am accessing the internet on the host system and working in the guest system.

The blue screen of death has the following error type in it SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Has anyone else been experiencing this ?

+1 vote

I am trying to virtualise a DOS guest on a windows 7 host because the physical box is going to break in short (386, very old). Unfortunately there is a software running using a hardware dongle on parallel port. AFAIK there is no virtual parallel port in vbox, and anyways it probably would not work with a dongle.

So how can I configure vbox to exclusively use the hosts parallel port?

+1 vote

Is it even remotely possible to run MacOSX (or Darwin) as VM under CentOS 5.10/ xen? Or am I better off not even trying and just getting a MacMini or MacBook to just jack into my LAN? I just need a 'build box' and possibly something to do light testing (eg does the program run? Does the GUI come up?).

I can cross-build for MS-Windows using mgwin32 and I have VMs for CentOS 6, Fedora, Ubuntu, Debian, etc. Only MacOSX is missing from the 'mix'.

+1 vote

When I run the code on my ID running from a windows 7 computer everything runs fine but when it is run on a different ID at night on the server it fails to finish.

A side question, is there a way of getting a log from a batch?

...