Windows 11 General Discussion

[bobbybluz]

I've been using this on Win 10 & 11 for years to block automatic updates. It works great. I enable updates only when needed.
Windows Update Blocker v1.8

 

[R-T-B]

Do you recall that registry key because in 2022 I did alot of tweaking to W11 in settings and registry, and it still got updates... Im really am thinking about having a debloat which guts windows update, and I just use powershell to install necessary security only updates, then an Aero glass Tool and maybe a control panel only tool lol

Yeah, the main setting is in group policy but it alone doesn't stop driver updates, just normal updates. I'll post the key you need in a second with an edit to this post. Also you need your "Device Installation Settings" set to not search for driver updates (usually typing "Device Inst" in the search box will display this dialog as the first result which I have no idea where they hid it otherwise). But between the regkey I'm about to post, the gpedit.msc setting of Disabled Automatic Updates, and that weird setting I just described, nothing has snuck up on me in nearly a decade.

Sorry for the wait but I actually have to get home first to consult my trusty "Windows notes.txt" document.

 

[lexluthermiester]

Yeah, the main setting is in group policy but it alone doesn't stop driver updates, just normal updates.

Nope, for that, one needs to disable the update service and the adjoining support services. This requires some registry fiddling and take ownership steps.

 

[R-T-B]

Nope, for that, one needs to disable the update service and the adjoining support services. This require some registry fiddling and take ownership steps.

I have never had to go that far (as long as gpedit works anyhow, so pro only). I'll post a guide shortly.

 

[lexluthermiester]

I have never had to go that far (as long as gpedit works anyhow, so pro only). I'll post a guide shortly.

I will watch with interest!

 

[Epaminombas]

Yes it is.
View attachment 388073
You were saying?

And you would be very wrong. I have seen and had to fix them personally, many of them on FRESH untouched installs, not updates.

So again, you were saying?


Which was meandering off-topic anyway...

What you are showing are i9 extreme, a line for industry and professionals.

most 90% of motherboards in the normal Intel 7 and 8 generation line do not have TPM

They started launching motherboards that are 100% compatible with the new generation of Windows 11 from Intel 9 generation onwards.


If you had to fix PCs with Windows 11 problems, then the problem was not the system, but a problem involving bad drivers, a third-party program or a lack of update.

If you do a fresh installation of WIndows 11 and disable Updates then it will cause a lot of problems.
Now if you install 100% of the updates you will hardly have any problems.

 

[lexluthermiester]

What you are showing are i9 extreme, a line for industry and professionals.

You said there were no Intel 7th gen series CPU's supported. I showed otherwise. Are you really going to nitpick?

most 90% of motherboards in the normal Intel 7 and 8 generation line do not have TPM

Moose Muffins!

They started launching motherboards that are 100% compatible with the new generation of Windows 11 from Intel 9 generation onwards.

No, that started with Intel 8th gen as denoted from the EXTENSIVE list of 8th gen CPU's supported in that list above.

If you had to fix PCs with Windows 11 problems, then the problem was not the system, but a problem involving bad drivers, a third-party program or a lack of update.

That would only be true if rolling back to 23H2 didn't work. It does, so it's 24H2, not the users, not the drivers, not anything else. It's problems with the 24H2 build of Windows itself.

If you do a fresh installation of WIndows 11 and disable Updates then it will cause a lot of problems.

That's not the problem. How do I know? Because of client PC's that have completely default installs and STILL have issues.

Now if you install 100% of the updates you will hardly have any problems.

That's not the problem. And not everyone is having the same issues.

However, those issues all magically go away when the machines having issues are rolled back to 23H2. So the problem, and try to follow along here, is 24H2.

 

[Onasi]

What you are showing are i9 extreme, a line for industry and professionals.

Fucking what? HEDT was always prosumer, not industrial.

most 90% of motherboards in the normal Intel 7 and 8 generation line do not have TPM

Fucking what v2? Intel PTT (their fTPM implementation) has been going since LGA1151 in 2015.

They started launching motherboards that are 100% compatible with the new generation of Windows 11 from Intel 9 generation onwards.

All of “incompatibilities” were strictly MS induced fake limitations. The existence of LTSC IoT proves this definitively. Before you try moving the goalposts - it’s the same OS as any other 11 at its core, it absolutely counts.

If you had to fix PCs with Windows 11 problems, then the problem was not the system, but a problem involving bad drivers, a third-party program or a lack of update.

Only a complete fool deals in absolutes. You are legitimately on a wrong forum if this is your position by default. While often issues indeed arise because of user error, claiming that “Microsoft dindu nuffin” in year 2025 is laughable.

 

[Epaminombas]

You didn't give me an example of a bug you had in 24H2 and you didn't even show the event viewer to confirm that it was a Windows process that caused this.

Microsoft wouldn't release a final version of Windows with so many problems.

And updating from above always has a chance of causing problems. Formatting is always the best way.

And this isn't exclusive to Windows.

iMac, iOS, Android, Linux always cause strange problems when you update from above.

So much so that if you go to an Apple store and complain that the update caused a problem, the first thing they do is format your iMac with a USB stick.

 

[Onasi]

You didn't give me an example of a bug you had in 24H2 and you didn't even show the event viewer to confirm that it was a Windows process that caused this.

Are you now replying to a wrong person? Because I said straight up that I had no issues with 24H2 on my personal rig. At work though? Fucking 24H2 still has issues pulling GPs from our domain controller unless forced via registry tweaks to kerberos. Why? Because MS just randomly changed how that bit of encryption works. I have no idea if that even was intentional. But, you know, I manage. No thanks to MS. I just take issue with your overall point, lack of knowledge and boiling down everything to a “it’s always the user who is at fault, just run Windows as MS recommends and you will have no problems”. Which is a ridiculous claim to make that even MS themselves seem to disagree with, seeing as how the most stable and dependable version by their own definitions is the one that explicitly DOES NOT require any of the TPM/VT/SafeBoot nonsense.

Microsoft wouldn't release a final version of Windows with so many problems.

Blud wasn’t here for ME or Vista, I suppose.

And updating from above always has a chance of causing problems. Formatting is always the best way.

You mean an in-place update, I suppose. Yeah, that’s often a recipe for issues. Though I have the same Win 11 install that I run since RTM that’s now on 24H2 and THAT never had issues, so… Oh, and it’s very, very non-MS stock, so I guess your point is once again moot.

Tl:dr - You are unironically a poster child for “knows just enough to be dangerous”. You are arguing cliches, often false, with people who know far more than you.

 

[windwhirl]

And to my ignore list they go.

Anyway. Windows 11 has it share of problems, some user generated, some Microsoft generated, some hardware manufacturers being dumbasses generated. And with trillions of trillions of hardware and software configurations combinations, even if the code was pristine, you'd still find someone with a problem not originated in PEBKAC.

 

[eidairaman1]

Yeah, the main setting is in group policy but it alone doesn't stop driver updates, just normal updates. I'll post the key you need in a second with an edit to this post. Also you need your "Device Installation Settings" set to not search for driver updates (usually typing "Device Inst" in the search box will display this dialog as the first result which I have no idea where they hid it otherwise). But between the regkey I'm about to post, the gpedit.msc setting of Disabled Automatic Updates, and that weird setting I just described, nothing has snuck up on me in nearly a decade.

Sorry for the wait but I actually have to get home first to consult my trusty "Windows notes.txt" document.

I will havetto go through gpedit and see again, and See if I did add a registry entry its been so long that i messed with that unit, it was just odd to see updates were pushed to it, it kind of makes me want to go nuclear option.

 

[Epaminombas]

Windows 10 supports Windows Server 2019 and 2022.

Windows 11 only supports Windows Server 2022 and 2025.

There are improvements in Windows Server 2025.

And your Windows Server needs to be updated to support Windows 11 24H2.

So I don't know how your work domain is configured.

There is also hybrid federation between Windows Server and Azure that gives you even more control over group policies between email/OneDrive accounts and Windows 11.

We are not going into details here.

Doesn't your company have an IT manager who takes care of Windows Server? AD? Federation? Email domain?

That's a problem for him to solve and not for Microsoft.

 

[Onasi]

Windows 10 supports Windows Server 2019 and 2022.

Windows 11 only supports Windows Server 2022 and 2025.

There are improvements in Windows Server 2025.

And your Windows Server needs to be updated to support Windows 11 24H2.

I literally told you what the problem is. It’s not the question of “support”. Our domain runs 2022. We’re not updating to 2025 right away just because MS broke a feature without telling anyone. The fact that the same GP config reception works just fine on 23H2 is indicative of a MS generated problem here.

There is also hybrid federation between Windows Server and Azure that gives you even more control over group policies between email/OneDrive accounts and Windows 11.

We are not running hybrid. Or fucking Azure. This work domain is not for email or OneDrive, it’s for actual meaningful things like research data sharing between workstations (running Enty builds) and collective control over complex scientific tools. The entire network is gated off and configured via the aforementioned domain manually. The fact that MS fucked up and made my work harder is on them.

Doesn't your company have an IT manager who takes care of Windows Server? AD? Federation? Email domain?

You’re speaking to one of those people.

That's a problem for him to solve and not for Microsoft.

Fuck right off with that. I already said that I found a workaround, but the fact remains that the feature is broken. I absolutely should not be required to manually change reg keys for kerberos because for some reason they forced RC4. And that’s just MY issue - I am hearing domain horror stories from a lot of my acquaintances, both on the server and post-join workstation side.

But yeah, I am ending this discussion. You are just clowning at this point and I have no desire to derail the thread.

 

[Epaminombas]

I don't know why you're so angry.

The same problems that an IT manager faces with Windows Server also happen to those who manage domains on a RedHat, for example.

It's up to the IT Manager to know how to apply and work around specific problems. And was this specific problem reported in documentation on the Microsoft website? It seems so, but you didn't give me any details.

If something had a negative impact and made the network unable to function, you can simply contact Microsoft and they will choose an available MVP to help you completely free of charge, if you have the original licenses.

The same thing would happen on a RedHat domain network.

Everything is solvable and if it doesn't and has a negative impact, you can contact Microsoft and they will give you money if any of their products cause you problems. This is even included in the license terms of use.