@Enthousiast : are you aware of this registry key : HKEY_CURRENT_USER\Control Panel\UnsupportedHardwareNotificationCache Some users say that a watermark is displayed This key is in my registry but not value (0, 1 ?) is supplied (I have no watermark on 22621.1265 installed with option 1 of the tool i.e UFWS 1.4).
Similar here. No watermark, but is it time to start worrying? btw: Tried to make the watermark show up by deliberately changing that key value. No watermark so far with either 1 or 0
My equipment is not compatible either and I get this and I use option 1 HKEY_CURRENT_USER\Control Panel\UnsupportedHardwareNotificationCache SV2 REG_DWORD 0x00000000 (0)
Is this related to this? https://forums.mydigitallife.net/th...-channel-ni_release.84990/page-2#post-1723016 This was with a certain ip build update and just once or twice.
I mentioned the article only because it comes from one of the main vendors and it says "Using a bootable WinPE image provides a simple process to deploy Windows 11 into a VM without a vTPM from the start that is fully supported by Microsoft and VMware." Some people might be reluctant to use scripts posted on forums in particular when it comes to using them for work related purpose. It is not necessary a matter of trust, but compliance rules and so on.
Hey @Enthousiast, appreciate this. I've used the version 2.2 way back when final 22H2 was released to Release Preview channel. What I want to ask you, is there any reason for me to recreate a new ISO using your latest v4.0? Will I missing something if I continue using the ISO created with v2.2? Thanks!
You have to update the Win_11_Boot_And_Upgrade_FiX_KiT_v4.0.cmd script and change line 19 to SET "DPaA=1" ; it concerns murphy78-DiskPart-Apply-v1.3.1
For regular clean installs of new builds from uupdump, option 1 is fine right for regular user? I don't actually need to bypass any of the requirements someone just said to run the isos through this script. thanks in advance nice work.
All first 3 options should be fine for clean installs. If you don't need to bypass any requirements (your hardware meets the win 11 minimum requirements) then there is no need for using this tool.
Problem with the fix-kit: Last desember I used the fix-kit for several upgrades from 10 to 11 without problems. Today I used the same generated iso as I used in december for a new upgrade, but now it fails with stop code "system service exception". Happens in last part of the upgrade after sveral boots. Found that this only happens when then lan-cable is plugged into the RJ45. With no cable, it runs and finishes without problem, win 11 showing fine on the desktop. Plugging in the cable, and the stop code pops up at once. Tried also a new upgrade from 10 to 11 with the cable in from the start, it fails with the stop code mentioned. Seems something has changed on the Microsoft side, have they tried to block the fix-kit ? Have I missed someting here ?