*** Microsoft Windows 11 Thoughts & Discussion Thread ***

Still running Windows 10 on my main rig..

Got a load of laptops with WIndows 11 on at work though, in the last few months people are moaning they're slow and randomly hang for 30 seconds when closing certain software (EHX more often than not) they never used too...
 
Still running Windows 10 on my main rig..

Got a load of laptops with WIndows 11 on at work though, in the last few months people are moaning they're slow and randomly hang for 30 seconds when closing certain software (EHX more often than not) they never used too...

I "upgraded" from 10 to 11 last year and for the first time in a long time, the process actually worked properly. The rest of the OS is the problem though. Still considering going back to 10 for now even though I will have to go the other way again later in the year.
 
Been on 11 for 2 years. Most of the 1500 users have no issues, but they are only given what they need.

Lots of problems with 24H2 though. Our MECM/SCCM solution can't even deploy an OS properly, so that's tomorrow's task
 
Just had it pull me out of fullscreen mode randomly the only thing I can see with a corresponding timestamp a notification that "Device Security: Local Security Authority Protection is Off" - when I click on that alert the corresponding setting page though shows it as on...

Never had these kind of issues with Windows 7 when properly setup.
 
Seems relatively widespread issues with it:



Tempted to just block updates for a bit until they've fully addressed it.

Can confirm, we got hit with it at the place I work. I don't deal with the Windows Updates side etc, but I know there was lots of unhappy people :D
 
They keep changing the installer and making it harder to bypass creating a ms account it's really annoying

Rufus and the OOBE\BYPASSNRO tricks still work I think.

It wouldn't surprise me if they try to remove any remaining bypass methods around the time Win 10 goes out of support.
 
Who says bugs are always bad...

We're aware of an issue with the Microsoft Copilot app affecting some devices. The app is unintentionally uninstalled and unpinned from the taskbar.

Note: This issue has not been observed with the Microsoft 365 Copilot app.

Microsoft is working on a resolution to address this issue.

In the meantime, affected users can reinstall the app from the Microsoft Store and manually pin it to the taskbar.
 
Decided to revert back to an old 10 install for a while to see how it would go and it was quite a surprise.

I really didn't realise how slow my 11 install had become and 10 was much faster in and around the OS, running software etc. Not tried gaming yet though, but I'm keeping 10 now for the foreseeable future.
 
Yeah if you decide to go to Win 11, I wouldn’t go beyond 23H2 imo. You can still download legit 23H2 iso, just not from MS directly.
 
Last edited:
  • Like
Reactions: TNA
Decided to revert back to an old 10 install for a while to see how it would go and it was quite a surprise.

I really didn't realise how slow my 11 install had become and 10 was much faster in and around the OS, running software etc. Not tried gaming yet though, but I'm keeping 10 now for the foreseeable future.

W10 support and updates from Microsoft ends in October this year.
 
W10 support and updates from Microsoft ends in October this year.

Of course, but I will decide then what to do: go back to 11, take the slight risk of going with 10 Enterprise IoT.

Right now, my five year old and highly abused Windows 10 install runs faster and better than my six month old Windows 11 23H2 install. Win 11 has been giving me various problems recently and that's without the elephant that is 24H2 that still hasn't been offered on my PC (meaning Microsoft still doesn't think it's safe enough to install). I can't be bothered to worry about 11 until it gets its act together.
 
It took me some time before I figured out why I could not map any WD My Cloud local drives on my home LAN. It turns out that 24H2 had made changes, not that I was aware of them....

Accessing a third-party NAS with SMB in Windows 11 24H2 may fail


A newly installed build of 24H2, seemed to lock that access down. Naturally Windows help was...............less than helpful.
 
Last edited:
It took me some time before I figured out why I could not map any WD My Cloud local drives on my home LAN. It turns out that 24H2 had made changes, not tha tI ws aware of them....


A newly installed build of 24H2, seemed to lock that access down. Naturally Windows help was...............less than helpful.
Ugh. It took me hours to get my shares working again and I use a physical cable directly between two PCs. Still not convinced the new way is more secure than the old way, but maybe I just don't know what I'm doing.
 
Personally think the SMB changes overall including the disabling of SMB1 by default are a good thing, the execution of the changes though is shocking (as is much of Windows development) and completely disregards the impact on the end user, changes not intimated to the end user and options are hidden away and/or fragmented, etc.
 
That's the point, in my case.
I had 24h2 running previously and all seemed well with shares to my WD Cloud devices, that was an updated Windows 11.

This time it was a fresh install of Windows 11 24h2.
When it was time to think about access to the drives I did not realise that those changes had been implemented, as it had previously worked fine.

My, My Cloud drives support SMB 1, 2 and 3. So I'm guessing that it is the SMD signed sharing that was the problem.

The only clue was an error trying to connect.

Whilst there can be reasoning as to why they do these things, it is not reflected when I tried to have access without being given information as to why it had stopped working.

So many YT videos and searching to try and figure it out and time lost.
Finding that information in a blog eventually brought a resolve.

If you happen to be on the Home edition of Windows then there is no gpedit tool, you will need to be familiar with Powershell.

It should not have to be so convoluted.
 
Last edited:
Back
Top Bottom