Win 11 Boot And Upgrade FiX KiT (v6.1f2 Released!!!)

hello. thanks for answering. I did not say that the iso is bad. read my previous message.
I simply said that after installing it, that message appears.
then we have to touch the registry? i search how. thanks.

do i have to create a new registry entry? I do not understand what you put me.

hello. both? I have to create 2 registry entries or modify 2 existing entries? Thank you.

 

Open a Command Prompt as Admin and run the below two commands.

Code:

reg add "HKEY_CURRENT_USER\Control Panel\UnsupportedHardwareNotificationCache" /v SV1 /t REG_DWORD /d 0 /f

Code:

reg add "HKEY_CURRENT_USER\Control Panel\UnsupportedHardwareNotificationCache" /v SV2 /t REG_DWORD /d 0 /f

 

Thank you. I have done it differently. the SV1 entry already exists in the registry. I have modified it to 0. On the other hand, I have created another entry equal to SV2 with the same value. it is right? only by modifying the SV1 input, the message no longer appears. Thank you.

 

The SV1 modification is for the 22000.xxx builds. That works. The SV2 entry is for the 225xx builds. I think people enter it for the new build release later this year, as a " just in case" entry so they can upgrade their system and hopefuly not worry about it.

So yes SV1 entry modification is all you need to modify as a minimum for the 22000 series..

 

I have added the other one too, so I have the system ready for the future. Thank you.

 

@Enthousiast Any chance to update your tool to integrate the watermark fix in new bulds (22000.588 +) by @BAU ?
[DISCUSSION] Windows 11 Official Build 22000.xxx (PC) [co_release]

 

It would be a little foolish and even a waste of time at present to consider adding a NAG MESSAGE/WATERMARK removal to the Fix, until one knows for certain how M$ plans to fully implement this "feature". For instance, it may be reloaded and registry entries amended every time one updates, making it usless to add a removal script to the fix for a build.

A little patience, and manually doing it is the better option at present.

 

Could be, but i suggested to add that option to avoid that infamous nag watermark on clean installations, i think no harm on trying

 

I hear you, but consider these points too. THE FIX is perfect. It works and does the job intended, allows Windows 11 to be installed on any machine. The old saying if it aint broke dont fix it comes to mind. Next point is we dont know what format, timing, etc M$ will roll out this Nag Message, and where it will appear. Til we know the full extend what M$ intends, one will chase their tail with no results. Finally, til we see what counter measures M$ tries to bring out to circumvent the ways people come up to remove the NAG, one cant fully incorporate its removal in any install.

On a side note, the people most hurt with the NAG/WATERMARK message is those selling dodgy machines with Windows 11 installed. At present they are selling machines as approved Windows 11 machines as they have that operating system on them. This message will undercut them, and make them do a lot of work. Instead of just loading W11 on dodgy machines and selling them, now they have to remove the NAG messages, and also deal with customers who get a update and the NAG message. A lot more work.

 

Who exactly would be selling "dodgy machines" with Windows 11? That is not something I've encountered, or expect to encounter. Perhaps in third world countries?

 

What is the readme password

 

I thought this was strange, but I made a .652 ISO and had to uncheck Enable EFI under Settings - System - Motherboard tab for the ISO to boot after using 2.2.

 

My previous message was for VirtualBox (sorry for any confusion), but I haven't tinkered with that variable since its inception. I'm using version 10.18a and it's UpdtBootFiles =1.

 

I mostly use W10UI on 10, not 11, Had a few minutes and I haven't made an ISO in awhile and just forgot to change the INI but I'll try to remember that for the future.