Yes my MV's networking is actually functional
Everything is fine now. Windows 10 Pro is activated
as expected :D. I bought Win 10 Pro on microsoft site yesterday. So this is a legal licence.
Since I dind't want to spend more time on fixing
this issue I called Microsoft Support Online directly to activate my Win 10 Pro. This is an option when you got this issue.
This is a option that you can use through "Parameters"
on Win 10 Pro (but I didn't remember where I clicked to get in Parameters options).
I called the number for my own country (France)
I tried to bypass all automatic digits suggested
by the automatic voice
I waited for getting someone on the call = 1
human (less than 1 minute)
He got the 6 digits. I had to install the applet
to access my PC remotely
I was OK that he could access my PC remotely.
He added the ID activation for my PC remotely.
PC was rebooted and it was OK.
I don't know why I got this issue after installing
all Xen PV Drivers 8.2.0 :(
Calling "Microsoft Online Support" seems to be
the easiest way to reactivate Windows 10 by entering your activation ID.
Not sure what’s happening then. Is your VM’s
networking actually functional?
Thanks for letting me know. I am on Windows 10
Pro version 1607 1493.0
I clicked on the trust dialog as you advised
me while I was installing drivers
I removed "the testsigning enabled" status and
I rebooted my VM
For activation I amstill blocked on this status
Same message then this one
I tried what it is recommended here
Unfortunately the only message I have is "Servers
are not available. Try later".
I will try later and see if I can get in to add
my own PC as suggested. But I guess it should take a while ( a few days or a few weeks?). Well I am not lucky
For Windows Update, it works but it always try
to reinstall the same update :( (KB4015438)
I suspect it is turning on
testsigning that is stopping Windows Update. You don’t need to turn
testsigning on for released drivers though. They are signed so should just be able install them (clicking through the trust dialog on the way). It’s only development builds that will need
testsigning enabled.
This weekend I set up Windows 10 Pro 64 Bits
as a VM (+ VGA Passthrough = GTX 680 harcoded to GRID K2).
I used Xen 4.3.4 on a Linux Kernel 3.19.
The VM is able to boot and works fine.
I installed all PV Drivers for 8.2.0. I added
bcdedit /set testsigning on
before installing all drivers as Administrator
(as recommended from INSTALL.cmd file ) .
Unfortunately now activating Windows 10 Pro does
not work anymore. I am able to work on the VM but no more Windows Update :(
Did I do something wrong?
FYI my VM was backed up through LVM system before
adding all Xen PV Drivers.
