Concern: Microsoft block win7/8.1 update with new CPU

Discussions about using Windows guests in VirtualBox.

Concern: Microsoft block win7/8.1 update with new CPU

Postby NoNoNo » 18. Mar 2017, 04:21

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?
NoNoNo
 
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

Postby socratis » 18. Mar 2017, 05:12

  1. 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.

  2. Win7 is already in extended support, i.e. security patches only.

  3. 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".

  4. 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".

Bottom line: scareware/fearware, click-for-ads articles on InfoWorld and Reddit and the likes... Thanks Microsoft...

 Edit: Updated on 2017-03-29 with the most recent information. 
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.
socratis
Site Moderator
 
Posts: 24377
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Concern: Microsoft block win7/8.1 update with new CPU

Postby NoNoNo » 23. Mar 2017, 22:14

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.
NoNoNo
 
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

Postby socratis » 23. Mar 2017, 23:27

I edited my post above to reflect the situation. From what I read, only point #1 changed. So far... ;)
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.
socratis
Site Moderator
 
Posts: 24377
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Concern: Microsoft block win7/8.1 update with new CPU

Postby socratis » 29. Mar 2017, 01:54

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.
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.
socratis
Site Moderator
 
Posts: 24377
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Concern: Microsoft block win7/8.1 update with new CPU

Postby NoNoNo » 29. Mar 2017, 07:22

oh well. as it happened, hopefully hiding KB4012218, KB4012219 & KB4012982 is the idea we can rely later.
NoNoNo
 
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

Postby socratis » 29. Mar 2017, 10:24

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!
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.
socratis
Site Moderator
 
Posts: 24377
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Concern: Microsoft block win7/8.1 update with new CPU

Postby AnrDaemon » 1. Apr 2017, 16:01

How about "synthetic CPU" support for Windows versions of VirtualBox, at last?
AnrDaemon
 
Posts: 106
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

Postby socratis » 1. Apr 2017, 16:56

What about it? What *is* it? The "synthetic CPU" I mean...
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.
socratis
Site Moderator
 
Posts: 24377
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Concern: Microsoft block win7/8.1 update with new CPU

Postby hmo » 16. Apr 2017, 12:38

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.)
hmo
 
Posts: 5
Joined: 16. Apr 2017, 12:32

Re: Concern: Microsoft block win7/8.1 update with new CPU

Postby socratis » 17. Apr 2017, 10:59

hmo wrote:Sorry, unable to post links directly as the rules forbid it
You could have copy/pasted the whole thing ;)



  1. In VirtualBox, clone an existing virtual machine. Either a linked clone or full clone is ok.
  2. Exit all virtual machines and VirtualBox also.
  3. At a command prompt, issue these commands:
    Code: Select all   Expand viewCollapse view
    "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
  4. Use the cloned virtual machine.
  5. When done with cloned virtual machine, delete it.
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.
socratis
Site Moderator
 
Posts: 24377
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Concern: Microsoft block win7/8.1 update with new CPU

Postby AnrDaemon » 28. Apr 2017, 21:40

socratis wrote:What about it? What *is* it? The "synthetic CPU" I mean...

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).
AnrDaemon
 
Posts: 106
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

Postby NoNoNo » 3. May 2017, 05:59

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)


AnrDaemon wrote:Linux VBox host offers an option to fake CPU identification for VM (called "synthetic CPU" or similar...

You hint an interesting experimental vbox function (ya I hear it first time :roll: )
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
NoNoNo
 
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

Postby AnrDaemon » 5. May 2017, 15:21

Found where I've seen it.
Code: Select all   Expand viewCollapse view
$ 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]

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.
AnrDaemon
 
Posts: 106
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

Postby cranium » 4. Jul 2018, 17:11

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!
cranium
 
Posts: 1
Joined: 4. Jul 2018, 17:06

Next

Return to Windows Guests

Who is online

Users browsing this forum: No registered users and 19 guests