Insider KB5015039 Windows 11 Insider Dev Build 25120.1010 (rs_prerelease) 22H2 - May 20

jimbo45 · May 21, 2022

I found the easiest way after installing on a VM was to attach a physical disk to the VM, boot into the VM, clone the VM disk to the physical disk , update the bootloader (on to the new physical disk -- can be but doesn't have to be a vhdx file) -- if cloning from vhdx file to non vhdx file ensure target disk has efi and msr partition and just clone the VM Windows "C" drive. Then install bootloader with bcdboot etc, and boot. If cloning from a non vhdx file just clone the Windows partition , don't copy the efi partition but install the bootloader to the efi partition after after cloning.

Bootloader should be installed to the efi file whether it's on a disk consisting of a number of vhdx files or a "standard disk".

You'll get a whole slew of "unknown device" but easily fixable :

Update the various device drivers from a previous W11 or even W10 "Real install" - I have all mine in a file on another disk and re-boot. You could mount a windows macrium backup image and then install from the windows driver store etc.

This even works if you have an "Unsupported" CPU so long as in your VM you can "poodlefake" the CPU into one that's supported by W11 -- QEMU/KVM allows you to specify various CPU options and topography irrespective of the Host CPU -and I think HYPER-V has similar. -- I had a supported one in my VM - Qemu 64 bit default hypervisor.

So after everything working again on physical machine device shows cpu instead of Intel Gen 6 (not supported) but :

Working perfectly -- laptop is perfectly fast enough for this

The VM hardware :

Note that the acpi x-64 cpu on the VM is carried over to the physical machine and the video driver (in my case the virtual VIO one from Red Hat will be replaced by the microsoft basic video driver on ist boot of the real machine so driver updates will fix that one as well.

So although a bit more effort this way avoids all the hassle in getting round all the fiddling with Iso's etc to avoid the checking whether windows 11 is capable of running on the machine or not.

If it won't run on a VM the chances are that it's a waste of time even thinking of trying to do a native install on a physical machine. .

You'll though still need to re-install applications that you only run on a physical machine e.g games etc. but it should all work easily enough.

Cheers
jimbo

brummyfan · May 21, 2022

I have a minor problem with this build, I need to press Power button twice when I cold boot, I have reverted to 22115 and updating to this build and see whether it fixes the problem.

jvickers · May 21, 2022

brummyfan said:
I have a minor problem with this build, I need to press Power button twice when I cold boot, I have reverted to 22115 and updating to this build and see whether it fixes the problem.

That doesn't sound like a windows problem since you OS hasn't loaded yet unless I'm misunderstanding.

jimbo45 · May 21, 2022

brummyfan said:
I have a minor problem with this build, I need to press Power button twice when I cold boot, I have reverted to 22115 and updating to this build and see whether it fixes the problem.

Power settings ???? -- laptop / desktop ??

Cheers
jimbo

dbartenstein · May 21, 2022

brummyfan said:
I have a minor problem with this build, I need to press Power button twice when I cold boot, I have reverted to 22115 and updating to this build and see whether it fixes the problem.

From a cold boot? The OS is not loaded yet. That sounds like a hardware issue.

jvickers · May 21, 2022

jimbo45 said:
Power settings ???? -- laptop / desktop ??

Cheers
jimbo

They're using a laptop according to their computer profile. Probably a h/w issue, though.

brummyfan · May 21, 2022

jimbo45 said:
Power settings ???? -- laptop / desktop ??

Cheers
jimbo

dbartenstein said:
From a cold boot? The OS is not loaded yet. That sounds like a hardware issue.

jvickers said:
They're using a laptop according to their computer profile. Probably a h/w issue, though.

I don't think it's a hardware issue because I don't have this issue in previous builds, I use only laptops and have tried different Power options, also tried disabling Fast start-up.

CountMike · May 21, 2022

brummyfan said:
I don't think it's a hardware issue because I don't have this issue in previous builds, I use only laptops and have tried different Power options, also tried disabling Fast start-up.

Could it be that instead of shutting off it goes to some kind of sleep mode ? Can be tested by removing all power if desktop or battery in case of a laptop. That's real cold BOOT.

cereberus · May 21, 2022

I do not know if it was this small update or the full upgrade to 25120, but it disabled my winre.wim.

My dev installation was set up with 3 partitions - efi, msr, C drive, and winre.wim is enabled with winre.wim being on the C drive. c:\recovery folder. Setting it up like this makes it easier to expand/shrink vhdx file (too complicated to discuss here)

After the upgrade, it created a new recovery partition with winre.wim, deleted winre.wim from C drive.

It should have enabled winre.wim, as it was in the recovery partition, but it did not do so.

Trying to renable it using reagentc failed. I tried the disable command, hoping it would move winre.wim to c:\windows\system32\recovery folder where winre.wim is parked when disabled.

However, it rejected reagentc disable command saying already disabled.

I manually copied the winre.wom and the reagent.xml file to c:\windows\system32\recovery folder, deleted the recovery partition, and then reenable worked.

As an aside, it is not easy to do that from file explorer as it does not give permission to view the recovery folders. I actually use the treesize app which is very handy at handling hidden files and folders - it seems to have "full admin" rights as if using the administrator account (it can be quite a dangerous tool in wrong hands).

brummyfan · May 21, 2022

@jimbo45 @dbartenstein @jvickers @CountMike
Thanks for the suggestions, I have resolved the problem, this is what I have done, pressed F9 followed by F10 in BIOS, then disabled fast start-up in Power options

Zardoc · May 21, 2022

I was able to do a clean install, and man that was fast. 5 minutes!!

So it is definitely driver related. I will try to cheat the pci.sys file

Pirilampo2 · May 21, 2022

Updated today moved from Beta channel to Dev channel, no problems but very time consuming to do it.

Zardoc · May 21, 2022

Nope, can't update. Can't find the driver because of crash and restore

svansiclen · May 22, 2022

Broke 3dmark, I thought my graphics cards were blown. Updated vbios, reinstalled drivers. Finally realized this build doesn’t want us benching in 3dmark. All other benchmarks like final fantasy and Heaven work fine, first time I’ve ever seen something like this in a dev build. Which sucks because in loved the cpu scheduler in this build.

conetzin · May 22, 2022

Are there already noteworthy changes in comparison to (RTM?) beta channel builds that justify switching to dev channel or is it only about minor experiments and changes? Search bar doesn't appear to be a biggie to me

krzysiek · May 22, 2022

hello I installed this build 25120.1000 but I don't have this search engine on my desktop there is no weather widget on the left side of the taskbar and it showed a watermark what is it all about?

CornishRattler · May 22, 2022

krzysiek said:
hello I installed this build 25120.1000 but I don't have this search engine on my desktop there is no weather widget on the left side of the taskbar and it showed a watermark what is it all about?

It's a dev build, there is a watermark, I'm sure we've been through this before. The search bar is being rolled out as per the release notes. I don't have it and if I did it would be disabled quick sharp

brummyfan · May 22, 2022

krzysiek said:
hello I installed this build 25120.1000 but I don't have this search engine on my desktop there is no weather widget on the left side of the taskbar and it showed a watermark what is it all about?

If you have the backup image of previous build, recover the image and update to this build and see whether it resolve the issue, it may have corrupted during the update.

Edwin · May 22, 2022

Desktop Search Bar can be enabled with the ViveTool, but, it seems pointless, redundant..., to me, anyway!

Winuser · May 22, 2022

Edwin said:
Desktop Search Bar can be enabled with the ViveTool, but, it seems pointless, redundant..., to me, anyway!

View attachment 29787

When it installed on my desktop, I moved it to my second monitor. About an hour or two later I turned it off and unchecked the auto start option. MS must still think that we are all using tablets and/or cell phones.

Insider KB5015039 Windows 11 Insider Dev Build 25120.1010 (rs_prerelease) 22H2 - May 20

TL;DR​

Changes and Improvements​

[General]​

Fixes​

[Suggested Actions]​

[Settings]​

[Task Manager]​

[Other]​

Known issues​

[General]​

[Live captions]​

About the Dev​

Important Insider Links​

Attachments

Well-known member

My Computer

Well-known member

My Computers

The lunatics have taken over the asylum

My Computers

Well-known member

My Computer

Well-known member

My Computers

The lunatics have taken over the asylum

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Dazed & Confused

My Computer

Well-known member

My Computers

Dazed & Confused

My Computer

Member

My Computer

Active member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

♦ ♦

My Computers

Well-known member

My Computers

Similar threads

TL;DR

Changes and Improvements

[General]

Fixes

[Suggested Actions]

[Settings]

[Task Manager]

[Other]

Known issues

[General]

[Live captions]

About the Dev

Important Insider Links