Concern: Microsoft block win7/8.1 update with new CPU
-
- Posts: 51
- Joined: 16. Apr 2015, 17:35
- Primary OS: Debian other
- VBox Version: PUEL
- Guest OSses: Windows XP(32bit) / Debian 8.x / Debian 7.x / Windows 7(32bit)
Concern: Microsoft block win7/8.1 update with new CPU
Please visit this KB article: https://support.microsoft.com/en-us/help/4012982/
Looks Ryzen / Kaby Lake CPU family got this problem with old windows version.
so, Does Vbox VM guest trip over this problem, too?
Looks Ryzen / Kaby Lake CPU family got this problem with old windows version.
so, Does Vbox VM guest trip over this problem, too?
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Concern: Microsoft block win7/8.1 update with new CPU
- It was formally announced on 2017-03-17.
It was experimentally deployed on 2017-03-21.
It was first reported as affecting VirtualBox VMs on 2017-03-29. - Win7 is already in extended support, i.e. security patches only.
- It won't affect you until 2020-01-14 (Win7) or 2023-01-10 (Win8.1).
It will affect you if you install KB 4012218 (March 2017 Preview of Monthly Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1), which includes an update described in KB 4012982 ("The processor is not supported together with the Windows version that you are currently using" error when you scan or download Windows updates),
and you are using an "Intel seventh (7th)-generation processor" or an "AMD Bristol Ridge". - There have been no reports yet for real computers, let alone virtual.
There first report was on 2017-03-29 in the thread: "Host win 10 64 home intel core i7 7th gen guest win 7 64".
Edit: Updated on 2017-03-29 with the most recent information. |
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 51
- Joined: 16. Apr 2015, 17:35
- Primary OS: Debian other
- VBox Version: PUEL
- Guest OSses: Windows XP(32bit) / Debian 8.x / Debian 7.x / Windows 7(32bit)
Re: Concern: Microsoft block win7/8.1 update with new CPU
Another news talk about this:
KB4012218, KB4012219: Windows Update processor generation detection
Rumor is KB4012218 & KB4012219 will deny windows 7/8.1 to get proper update with current generation CPUs. It may not ignore easily due to dependency.
KB4012218, KB4012219: Windows Update processor generation detection
Rumor is KB4012218 & KB4012219 will deny windows 7/8.1 to get proper update with current generation CPUs. It may not ignore easily due to dependency.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Concern: Microsoft block win7/8.1 update with new CPU
I edited my post above to reflect the situation. From what I read, only point #1 changed. So far...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Concern: Microsoft block win7/8.1 update with new CPU
We have the first report of a VM showing the CPU warning: "Host win 10 64 home intel core i7 7th gen guest win 7 64".
For the record, the CPU was an Intel i7-7700HQ @ 2.80GHz.
For the record, the CPU was an Intel i7-7700HQ @ 2.80GHz.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 51
- Joined: 16. Apr 2015, 17:35
- Primary OS: Debian other
- VBox Version: PUEL
- Guest OSses: Windows XP(32bit) / Debian 8.x / Debian 7.x / Windows 7(32bit)
Re: Concern: Microsoft block win7/8.1 update with new CPU
oh well. as it happened, hopefully hiding KB4012218, KB4012219 & KB4012982 is the idea we can rely later.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Concern: Microsoft block win7/8.1 update with new CPU
The "March Preview" updates will become the official "March" updates. So if you block them, you're in effect blocking the updates. All of them.
- Microsoft: Mission accomplished!
- Microsoft: Mission accomplished!
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 134
- Joined: 7. Feb 2010, 23:41
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Ubuntu Linux, Windows
Re: Concern: Microsoft block win7/8.1 update with new CPU
How about "synthetic CPU" support for Windows versions of VirtualBox, at last?
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Concern: Microsoft block win7/8.1 update with new CPU
What about it? What *is* it? The "synthetic CPU" I mean...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Concern: Microsoft block win7/8.1 update with new CPU
Google for "For you testers: Here’s how to spoof a Kaby Lake processor inside a VirtualBox Win7 VM", comment 108402 contains the hint. Works for me, WIndows update works again in my Win7 VM running on a Kaby Lake-based host.
(Sorry, unable to post links directly as the rules forbid it: "You must be a member for 1 days and have 1 posts before you can post urls.)
(Sorry, unable to post links directly as the rules forbid it: "You must be a member for 1 days and have 1 posts before you can post urls.)
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Concern: Microsoft block win7/8.1 update with new CPU
You could have copy/pasted the whole thinghmo wrote:Sorry, unable to post links directly as the rules forbid it
- In VirtualBox, clone an existing virtual machine. Either a linked clone or full clone is ok.
- Exit all virtual machines and VirtualBox also.
- At a command prompt, issue these commands:
Code: Select all
"C:\Program Files\VirtualBox\VBoxManage" modifyvm "Put target virtual machine name here" --cpuid-portability-level 1 "C:\Program Files\VirtualBox\VBoxManage" modifyvm "Put target virtual machine name here" --cpuidset 00000000 00000016 756e6547 6c65746e 49656e69 "C:\Program Files\VirtualBox\VBoxManage" modifyvm "Put target virtual machine name here" --cpuidset 00000001 000806e9 00100800 7ffafbbf bfebfbff "C:\Program Files\VirtualBox\VBoxManage" modifyvm "Put target virtual machine name here" --cpuidset 80000000 80000008 00000000 00000000 00000000 "C:\Program Files\VirtualBox\VBoxManage" modifyvm "Put target virtual machine name here" --cpuidset 80000001 00000000 00000000 00000121 2c100800 "C:\Program Files\VirtualBox\VBoxManage" modifyvm "Put target virtual machine name here" --cpuidset 80000002 65746e49 2952286c 726f4320 4d542865 "C:\Program Files\VirtualBox\VBoxManage" modifyvm "Put target virtual machine name here" --cpuidset 80000003 37692029 3035372d 43205530 40205550 "C:\Program Files\VirtualBox\VBoxManage" modifyvm "Put target virtual machine name here" --cpuidset 80000004 372e3220 7a484730 00000000 00000000
- Use the cloned virtual machine.
- When done with cloned virtual machine, delete it.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 134
- Joined: 7. Feb 2010, 23:41
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Ubuntu Linux, Windows
Re: Concern: Microsoft block win7/8.1 update with new CPU
Linux VBox host offers an option to fake CPU identification for VM (called "synthetic CPU" or similar, I[m not in reach of my Linux VM host ATM).socratis wrote:What about it? What *is* it? The "synthetic CPU" I mean...
-
- Posts: 51
- Joined: 16. Apr 2015, 17:35
- Primary OS: Debian other
- VBox Version: PUEL
- Guest OSses: Windows XP(32bit) / Debian 8.x / Debian 7.x / Windows 7(32bit)
Re: Concern: Microsoft block win7/8.1 update with new CPU
If you willing to modify GUEST windows system file. this may work for you: Find out at https://github.com/zeffy/kb4012218-19 (all appreciation to him)
Below is no proof, just my imagination:
swap old wuaueng.dll under \Windows\System32\
This way may work in short term. (in the lazy-man style)
synthcpu was mentioning in 5.0 manual. I try to apply under 5.0.40 but no avail.
Also look bug 9524: SynthCPU: Windows installer crashed
Below is no proof, just my imagination:
swap old wuaueng.dll under \Windows\System32\
This way may work in short term. (in the lazy-man style)
You hint an interesting experimental vbox function (ya I hear it first time )AnrDaemon wrote: Linux VBox host offers an option to fake CPU identification for VM (called "synthetic CPU" or similar...
synthcpu was mentioning in 5.0 manual. I try to apply under 5.0.40 but no avail.
Also look bug 9524: SynthCPU: Windows installer crashed
-
- Posts: 134
- Joined: 7. Feb 2010, 23:41
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Ubuntu Linux, Windows
Re: Concern: Microsoft block win7/8.1 update with new CPU
Found where I've seen it.
Unfortunately, that host is not up for experimentation.
I strongly suggest you don't try to toggle this flag on a live system. If you want to experiment, install a new system with this flag turned on.
Code: Select all
$ vboxmanage --version; vboxmanage modifyvm | grep -EC3 "modify|synth"
4.3.38r106717
Usage:
VBoxManage modifyvm <uuid|vmname>
[--name <name>]
[--groups <group>, ...]
[--description <desc>]
--
[--vtxux on|off]
[--pae on|off]
[--longmode on|off]
[--synthcpu on|off]
[--cpuidset <leaf> <eax> <ebx> <ecx> <edx>]
[--cpuidremove <leaf>]
[--cpuidremoveall]
I strongly suggest you don't try to toggle this flag on a live system. If you want to experiment, install a new system with this flag turned on.
Re: Concern: Microsoft block win7/8.1 update with new CPU
The suggested vboxmanage lines :
vboxmanage modifyvm "Put target virtual machine name here" --cpuid-portability-level 1
.....etc..
vboxmanage modifyvm "Put target virtual machine name here" --cpuidset 80000004 372e3220 7a484730 00000000 00000000
worked for me on Linux with WIn7 Pro vm. I now get updates again. I did try editing with the cpu strings of the windows registry under HKLM>Hardware, first, but had no success.
Thanks!
vboxmanage modifyvm "Put target virtual machine name here" --cpuid-portability-level 1
.....etc..
vboxmanage modifyvm "Put target virtual machine name here" --cpuidset 80000004 372e3220 7a484730 00000000 00000000
worked for me on Linux with WIn7 Pro vm. I now get updates again. I did try editing with the cpu strings of the windows registry under HKLM>Hardware, first, but had no success.
Thanks!