24H2 problems hitting us hard - Is it just us?
Posted by Bashkit@reddit | sysadmin | View on Reddit | 209 comments
Intune Windows shop - many devices have updated to 24H2 and we are getting slammed with all kinds of new problems. Each user has a different issue, so far we have seen:
- WebView2 related errors in Teams
- SMB share takes minutes to drill into each subfolder
- Autodesk products fail SSO
- Outlook attachments won't appear in message
- Outlook attachments won't open within desktop app
- Storage related BSOD on brand new ThinkPad
- Print queues clogging, that's if the driver wasn't randomly deleted from the machine.
- I know I'm forgetting more
Sometimes a rollback fixes it, sometimes more problems pop up. I've seen my share of bad updates but this one is putting a strain on the helpdesk: is anyone experiencing this?
Shadiac76@reddit
24H2 mangled every machine it got on in our domain. Serveral services no longer function. Search indexing being a major one which casues file explorer to lock up when navigating to any folder. Office desktop apps refuse to open. A few other items. SO far best guess is it's being caused by our TrendMicro endpoint protection corrupting something at some point as they only way I have been able to reoslve the problem other than a rollback to 23H2 is to install a repair version 24H2 through recovery after disbaling the endpoint protection. If I don't disable it, the issue remains after the repair.
dazclayton@reddit
Anyone getting a lot of WHEA errors from the processor since upgrade from 10-11??
Tuivian@reddit
to add to the list - Outlook Word attachments get stuck opening in Protected view for well over 60 seconds. If you turn off protected view (which is what Microsoft Support reccommended I do), it resolves it... not the best solution.
way__north@reddit
Interesting, we've had some cases of printing trouble the last days. I'll check out which verions are running.
Otherwise, been testing 24H2 the last weeks with inconsistent results..: - not all my test pcs are recognized as "applicable". Some on win10 22H2, some on win11 23H2
1 did the update , but hangs at 84% after rebooting
1 took forever to login after updating
way__north@reddit
update: print issues does not seem to be related to 24H2.
IndyPilot80@reddit
We have 24H2 on a test group, including myself. Haven't noticed any issues at all.
colt2x@reddit
Push it in production, problems will come :D
burnte@reddit
My zebra is on a Raspberry Pi running CUPS, it’s never given me a single issue, unlike direct windows printing to Zebra printers which is much more as you state. 🤣
Mr_ToDo@reddit
I'm betting my zebra experiences would be a lot better if the people I deal with didn't keep buying the "cheapest" ones you can get.
Why does anyone even sell a printer who's default feedback is a blinking LED? That's the kind of stuff we had in the 90's on the discount printers.
pdp10@reddit
Some categories of printers got into a "race to the bottom". Then vendors were practically giving away the printer and making their money back on the consumables.
That era set a lot of expectations with the end-user community. Some sites today can only get big enterprise printers if they're called "copiers" and paid for on a subscription basis.
Hardware has for the most part stopped getting cheaper a while ago, but the end-user community often finds it convenient to assume that it's cheaper than ever. Anyone who tells them otherwise is inconvenient.
lpmiller@reddit
sometimes, it's because you didn't look at them at all and they get a little jealous.
hiveminer@reddit
It’s actually because you look at them as being white with black stripes, when Infact they are black with white stripes!!
This_guy_works@reddit
It will be a cold day in hell before I recognize zebras as being black with white stripes.
Jawb0nz@reddit
I have one under my desk and occasionally kick it when I forget it's there. Is that bad?
lpmiller@reddit
well, they tend to roam in packs, so...
techie_003@reddit
You'll be needing to look at a replacement for WSUS..
"As part of our vision for simplified Windows management from the cloud, Microsoft has announced deprecation of Windows Server Update Services (WSUS). Specifically, this means that we are no longer investing in new capabilities, nor are we accepting new feature requests for WSUS. However, we are preserving current functionality and will continue to publish updates through the WSUS channel. We will also support any content already published through the WSUS channel."
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/windows-server-update-services-wsus-deprecation/ba-p/4250436
https://www.reddit.com/r/sysadmin/comments/1fljd6h/microsoft_has_officially_deprecated_wsus/
IndyPilot80@reddit
If I'm reading it right, WSUS is included in Server 2022 and 2022's "extended" date is 2031. Also looks like WSUS will be in Server 2025. So, we're good until 2031.
As for "no longer investing in new capabilities" for WSUS, WSUS has a category specifically for "WSUS Updates". We've been running WSUS for years and have never seen any WSUS updates. So, my response is how is that any different than how its been for the past many years?
Seth0x7DD@reddit
Stuff can take ages to go from deprecated to gone. I'd be surprised if it wasn't the same for WSUS.
_totally_not_a_fed@reddit
That's hilarious considering WSUS has been the exact same steaming pile of garbage for many years
Jawb0nz@reddit
Zebra setter upper for years in the past. Disliked them greatly.
IndyPilot80@reddit
When they work, they work and they are fairly low maintenance. When a config goes wrong, a driver gets messed up, or you are running more than one Zebra printer on one workstation, it's a nightmare.
Jawb0nz@reddit
Ours are all server based. We moved from direct connect some time ago for obvious reasons. I agree that when they work, they just work, though. Tinkering in ZPL was kind of fun too.
poorest_ferengi@reddit
I moved us from the big ZM400/ZT410 Industrial printers to Gk420d/ZD620 printers and have had most issues disappear. If you aren't approaching the max label/DeltaT of the ZD620 and can deal with the fact they don't auto roll up the label backing, I'd recommend a trial of the smaller ones if you are primarily having issues with the Industrial Printers.
_Blank-IT@reddit
Got a pair of the GK420d model too and it's been pretty painless.
TinyBreak@reddit
sort of surprised the zebra printer didnt catch fire to be honest.
You laugh, but that has happened to me before.
todbanner@reddit
My org suffered this one too! Wrecked half the building with the fire suppression system.
Shendare@reddit
https://en.wikipedia.org/wiki/Lp0_on_fire
Altruistic-Subject-4@reddit
TIL! Thanks
Alaknar@reddit
Same here. Got three systems upgraded so far, nobody's complaining. The next 5 are scheduled for next week, this one will include users' boxes, so we'll see what they say.
Lukage@reddit
Same, that's the only issue I've seen.
santaclaws_@reddit
Ah, Windows. That IT full employment program.
0RGASMIK@reddit
I know a large company with no helpdesk, all Mac’s just have one guy that manages MDM and another that handles all the accounts.
everythingelseguy@reddit
Try running Chromebooks - honestly it is fkn bliss and I will be moving my current employer onto them after these laptops run out.
Shit just fkn works on them
fattes@reddit
Sounds like it’s ez pz
GBICPancakes@reddit
It is. I support both Macs and Windows, and a properly setup Mac fleet is a dream. It's not perfect and man do they drive you nuts sometimes, but nothing like the Windows side.
BasicallyFake@reddit
how many properly setup windows environments have you seen though....
GBICPancakes@reddit
Yeah that must be it. I've spent almost 30 years in IT, from the WinNT3.51 days to now. Supporting everything from schools, governments, large Fortune500 companies, lots of small businesses. Spoken at Microsoft conferences.
But yeah, I've probably never seen a proper Windows environment. :)
segagamer@reddit
Well, you're also comparing an on-prem domain environment to an MDM one...
GBICPancakes@reddit
Am I? All I said was Mac networks are less of a pain to manage than Windows. That goes for on-prem and MDM. I'd place JAMF or Mosyle over InTune any day of the week, and I'd rank ABM/ASM over AutoPilot for DEP.
A lot of that is Apple's strict control and management of the entire hardware/OEM process vs Dell/HP/Lenovo+Microsoft, but the point stands.
Now Macs without an MDM and only on-prem are tougher, and there can be an argument there that Windows is easier to manage, particularly in the post-NetBoot world where my beloved DeployStudio is no more, but that hasn't been a 'proper' Mac deployment in years and years.
You're entitled to your opinion - all I'm saying is, as someone who manages both ecosystems, I know which one is less of a hassle to me.
My ticket rates and issues per-device appear to agree with me.
segagamer@reddit
Yes, but I'm stating you're comparing Apples to oranges with you're "I've been doing it since 3.1 days" statement. MDM is not Group Policy/A domain.
Now, comparing JAMF to Intune, that's more like it, but also not a "managing Windows" thing exclusively either, since Intune isn't as good as JAMF with managing Macs either.
GBICPancakes@reddit
Comparing InTune to JAMF for Mac support is never going to go well for InTune, but I'm saying InTune for Windows support also isn't as good as JAMF or Mosyle for Mac support. :)
I'd compare an AD domain with GPOs to MacOSX Server and Workgroup Manager/MCX, which is now firmly in the dustbin of history (since Apple has no qualms about nuking older tech and zero interest in backwards support, while Microsoft is committed to keeping tech functional and providing backwards support for as long as possible)
In the NT days (pre-AD) I'd compare it to AppleShareIP and maybe At Ease (although back then I'd compare At Ease to Novell Zenworks before anything Microsoft had)
I still have many clients using on-prem AD, both for Windows and for Mac (people who grudgingly retired Mac servers for Windows Servers after I pestered them for 5 years or so) but if I get the option to "start fresh" it's going to be MDM-based as much as possible for both platforms. EntraID/InTune is slowly getting better, although it's hard to say goodbye to GPOs. It was much easier to drop MCX support on the Mac side and go with MDMs there, because the plist config file structure is easier to drag along to the MDM, whereas GPO-to-MDM you gotta lean heavily on registry keys.
Dealing with ASM/ABM and the whole Apple Configurator thing is a pain, but man it used to be much worse. When they first started doing MDM stuff (with shitty Profile Manager) it was a royal pain getting the VPP/DEP stuff working. Believe it or not, ASM/ABM is a vast improvement. Still a right pain when clients just buy random Apple gear and you gotta hand-enroll the devices.
not_logan@reddit
We have about 2000 people mostly on Macs. We also have an extensive helpdesk which spends most of their time dealing with Office365 and Teams. Even say they also responsible for internal IT infrastructure such as WiFi and running servers for finance
pdp10@reddit
You laugh, but every enterprise we saw move from a comparable system to a Windows-based system, had to more than double their techs to service everything. Part of it was just sheer complexity, and part of it was a severe lack of options with automation, scripting, and remote management.
This held true for VMS-based environments, Unix-based environments, DOS/Netware-based environments, and from what we could see, also Appletalk Mac based environments which are more inherently limited. I'll leave out mainframe and OS/2 as none we saw were like-for-like at the time.
In principle, it seems like the type of extensive login scripting used with Netware/DOS could have been applied to NT/Windows, but we never saw that in practice.
santaclaws_@reddit
I do laugh. Managing about a dozen VMWare servers hosting 5 windows instances each kept me quite busy for a long time.
NowThatHappened@reddit
If it wasn't for Microsoft, we'd all be out of a job :)
IdidntrunIdidntrun@reddit
That's why I'm concerned when the execs of my current company wanna move from Windows to a containerized VDI environment..like wtf would I do all day lol
NowThatHappened@reddit
CDI is gaining ground and does have some advantages over discreet desktops but only time will tell.
andykn11@reddit
Learn a whole NEW world of pain.
jwatttt@reddit
Exactly had this update ruin two people's computers so far. So bricked it won't even go into safe mode.
vodevil01@reddit
Windows Update didn't propose 24H2 on any of my 5 computers so, I bêta it's an insider version., so why are you complaining ?
Emotional_Garage_950@reddit
it’s not insider anymore it is general release at this point
moventura@reddit
I'm getting problems with dot net installing on new 24h2 machines that I'm rolling out :(
CrestronwithTechron@reddit
I’m entirely convinced nobody tested this update. It’s a heap of junk even for consumer side. They’ve broken Easy Anti Cheat as well had introduced a 8GB cache file you can’t delete.
Doso777@reddit
Windows Insider beta test was going for quite some time.
Probably not broken, just by design to get faster and smaller updates.
ErikTheEngineer@reddit
Problem is that the insider program isn't enterprises with not-perfectly-behaved software. It's PC enthusiasts and gamers. None of the edge cases even get looked at until the software is out and a big enough customer manages to break out of ticket jail to flag an issue to the developers.
thortgot@reddit
We use Insider to validate our software stack before release and report issues with it to Microsoft before release. If you aren't acting as a bit of QA for Microsoft and your vendors your issues don't get fixed.
Expensive but it allows us to deliver a much more stable solution.
Heck if you aren't large enough to have proper testing, just roll it out to half your IT endpoints. You'll find the pain points relatively quickly.
ErikTheEngineer@reddit
How do you report issues? I doubt they listen to comments in the Feedback Hub, so do you have to go through an account manager and have Premier Support?
thortgot@reddit
Yes we have both.
pdp10@reddit
Everybody wants everyone else to go first and do the QA and UAT for the developer.
CrestronwithTechron@reddit
That may be true, but it ultimately feels like this never got tested.
tankerkiller125real@reddit
Maybe instead of using shitty Kernel level software that can take out a computer with one simple screw up, not to mention become a massive attack vector if there's ever a zero day. Game devs should focus on novel anti-cheat methods within the game itself. Pro level cheaters run the cheats on a second computer anyway.
SPOOKESVILLE@reddit
Kernel level anti-cheats definitely do suck, but they are the most effective way to prevent cheating in a game. It is a night and day difference when a popular game doesnt have a kernel level anticheat. Sounds like Windows11 is trying to address this by removing most security features from the kernel level, so we'll see how that goes.
Adnubb@reddit
I would say it's debatable if it's the most effective way to prevent cheating. Maybe the easiest/cheapest way to implement, but not the most effective way. Making the game server perform sanity checks compared to the game rules would be more effective imho.
But even if it truly was the only effective way, I don't feel like such hugely invasive method should be allowed by the OS. The potential for abuse is just too great. So I'm glad MS is at least addressing this. (Even though it doesn't really apply to me anymore. All my gaming and home use has been on Linux for at least half a decade now. I'm only dealing with MS at work nowadays, so no EAC there, lol)
SPOOKESVILLE@reddit
It actually should make your life a lot easier on linux, since it’ll be much easier for companies to get their games working on Linux now
segagamer@reddit
But Linux is compatible with Windows stuff, so companies have no reason to make Linux stuff.
SPOOKESVILLE@reddit
It’s the anti cheats I’m referring to. Things could definitely be easier now, but last time I poked around with Linux gaming a lot of things with kernel level anti cheats were messy. There’s things like Proton that fix this, but I dont know how far all of that has come. MS taking the security features out of the kernel will definitely make things easier for everyone. Well…I shouldn’t say definitely…it is Microsoft we’re talking about.
Mr_ToDo@reddit
Sanity checks is how it was before kernel. Lots of different kinds of cheats to account for though.
But if you're looking for the actual most effective way to prevent cheating we've already found and abandoned it. Server rendered gaming. With that the only real cheats left on the table are probably aim bots and they'd have to use visual cues instead of the normal game data like before(and I'm betting the false positives would give those away a lot easier). Pity that doing that tends to give such a shitty gaming experience.
fizzlefist@reddit
Considering Crowdstrike caused one of the biggest outages ever by having kernel level access…
SPOOKESVILLE@reddit
Ya, that’s pretty much the main reason MS is trying to move things out of the kernel. They got so much bad press for CS screw up even though it wasn’t their fault
dracotrapnet@reddit
I say detect cheaters and put them into their own playground, nice the engine down to be a little less responsive and charge admission to watch the chaos.
SnakeOriginal@reddit
About 7k endpoints so far, 1 required newer GPU driver, otherwise no problems
marcoevich@reddit
Regarding your SMB share, disable the preview pane in Windows Explorer. That can speed it up a lot!
Krisenmanager@reddit
I'm sorry for you, but I want to thank you/your team for signing up your users for the 24h2 beta test. This is the only way to improve the product so that we can use it productively soon.
sybrwookie@reddit
Yea, hearing people go to 24H2 right now is absolutely wild. We're just finishing up getting the last stragglers to 23H2 and have zero plans to move off of there until we're forced to do so by it EOL'ing in like....2 years IIRC.
lordmycal@reddit
I think it makes a lot of sense why people would want to. If you're upgrading Windows 10 machines, why not upgrade them to the latest version of Windows 11 so you won't have to touch them for a while? If you do adequate testing and there aren't any major issues in your environment, then you might as well.
So far, the only problem I've seen in my environment is that Crowdstrike doesn't support 24H2 yet, so the sensors run in Reduced Functionality Mode.
THe_Quicken@reddit
Exactly this. I think it was that 22h2 had a bug that broke some firewall functionality, so many complaints in the MS forums….no confirmation from Microsoft. 6 months later MS releases an update and in the fix notes they mention it corrects the firewall bug that they’ve basically been gaslighting us in the forums for the last six months. You’re a cowboy if you are pushing this update this soon.
Bashkit@reddit (OP)
We just moved from domain GPO and WSUS to Intune after 23H2. We set the target release to stay at 23H2 but I guess we did something wrong...
deltashmelta@reddit
We use the "feature" update tab, in the intune web GUI, to deploy and lock to a specified version.
deleteallcookies@reddit
Did you set up update rings with quality and feature deferral dates? The target release is supplemental to that but I think the update rings take precedence.
KaptainSaki@reddit
Just finished installing 22H2 today, no bugs so far!
New-Pop1502@reddit
🫡
jahermitt@reddit
🫡
Away-Ad-2473@reddit
Agreed. I haven't even deployed the update to the IT department yet and then would be at least a few months before we'd roll it out to rest of the company.
Zealousideal-Many682@reddit
I've not noticed an increase in problems on 24H2, but we will have to see as time goes on.
thortgot@reddit
If you are getting different issues for each user that would indicate to me that your baseline GPO/CSPs are a bit loose.
Do your share servers have SMB2 enabled? If so, turn it off that will be your root cause for SMB issues.
Whats your WebView2 error?
Our Autdodesk SSOs without issue.
No BSOD issues on our systems though though we are pretty modern on our endpoints.
AlexisFR@reddit
Well there's a reason why it's not deployed on windows update yet!
RCTID1975@reddit
But it is....
bornnraised_nyc@reddit
Killed the SIM card in a few X1s with 5G modems (wtf?) but otherwise no issues reported
Chunkycarl@reddit
Got hit with the BSOD on a fresh, out the box, machine today…
Lukage@reddit
You've got OEM with 24H2 or are you suggesting you built new images to have it in the initial deployment?
Chunkycarl@reddit
Machines are auto updating during configuration, the blue screening during the reboot. Had to go back to the good old offline setup to get around it (which it feels like Ms are making harder and harder to do)- just adds a whole bunch of extra steps to what should be a simple build :(
joshtaco@reddit
we have about 7000 users on it 24H2 now...put them on immediately. No issues seen, they don't even have a clue anything happened to be honest
ReputationNo8889@reddit
And we are still biting our nails for a windows 10 to 11 upgrade ...
joshtaco@reddit
we had ours all done 2+ years ago
ReputationNo8889@reddit
Im really happy for you!
If it were for me this would also be done by now. But our org structure is rather complicated and i'm beeing blocked by everyone because "Some apps might not work with windows 11" and "We have old devices". When i ask, which ones, i get met with silence. They just block as much as they can ... But with the sunsetting of Windows 10, i finally have enough leverage to force them. With CA beeing implemented already, everyone is aware that Windows 10 devices can not login after 14th October 2025.
Finally some gears started turning an i now finally have the greenlight for our 2 stage rollout. Until end of this year every one can upgrade voluntairy, start of next year it will be forced with our default update rings. This got everyone starting to order new equipment to replace the non Win 11 capable hardware.
From the looks of it we may actually hit the deadline spot on, with an estate of about 1000 Windows devices.
7ep3s@reddit
for me the biggest question is why is it on 300 of my workstations when we don't have it deployed, there is no feature update ring set up for it and we have target release version policy set up for 23H2...
MFKDGAF@reddit
Did you not test 24H2 internally before pushing it out to your entire company? 🤦♂️
Alway test internally to your department first. Then do a test group to a few users per department. Then deploy to the rest of the company.
MuffelMonster@reddit
Let me check.....
$% uname -a Linux daddel 6.10.11-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.10.11-1 (2024-09-22) x86_64 GNU/Linux
Yes, it does.
users-should-be-shot@reddit
Our VOIP provider has shit the bed on 24H2
agentofvictory@reddit
Quite a bit of issues that you described were seen in a small number of users who updated to 24H2. A lot of vendors also issues statements that 24H2 is. Breaking their shit.
Did you per chance have Crowdstrike installed? We tested by uninstalling on a user and it seems to fix ALL their issues. CS's response? 'Yeah we're no going to update that until November.'
noobposter123@reddit
Try upgrading to Windows 10 IoT Enterprise LTSC 2021? 😉
https://learn.microsoft.com/en-us/lifecycle/products/windows-10-iot-enterprise-ltsc-2021
Michal_F@reddit
The storage issue can be related to WD SSD ? I just read it yesterday ..But there is registry workaround until FW fix for SSD will be available. https://www.neowin.net/news/registry-hack-fixes-wd-sn770-sn580-windows-11-24h2-blue-screens-bsod/
Western Digital NVMe SSDs, wherein their drives are blue screen crashing after updating to Windows 11 24H2. The issue seems to be happening on WD_Black SN770 and WD Blue SN580,
TechIncarnate4@reddit
No. We do not move quickly to these yearly updates and wait a few months for things to shake out.
ReputationNo8889@reddit
Right, let those Home users test it first
Mobile_Analysis2132@reddit
We have a user on Windows 11 updated and it broke his VPN. All sorts of troubleshooting and nothing made sense. They rolled back the update and the VPN worked immediately.
allw@reddit
Add to this struggling to capture the image for use on AVDs. And of course MS has some rediculous way of you never being able to edit stuff in a sensible way.
Unique_Investment_35@reddit
Add Defender Application Guard no longer works.
The notes say it should function as before for existing existing PC's, but won't be an option to deploy afresh.
It removed it from machine that was running it prior to the update.
korvolga@reddit
TLDR, do not upgrade to 24h2 yet.
mbkitmgr@reddit
I've had a number of users calling to report odd things across multiple orgs, all have been on 24H2
We have to cut MSFT some sack, it's not as if they've updated OS's and Apps before today :(
TrowaB3@reddit
No because moving over to a new OS, especially when Microsoft themselves say it has issues, is insanity.
Why aren't you blocking update??
brothertax@reddit
24H2 broke web sign-in, which is essential for passwordless environments (or setup techs wanting to use TAP without having to bug the user for their password).
jenmsft@reddit
There's a fix for this in Release Preview: Releasing Windows 11 Build 26100.2152 to the Release Preview Channel | Windows Insider Blog
autocuck9000@reddit
Re: Outlook issues - those should be primarily impacting your users on new Outlook and users Outlook for Mac.
Ihaveasmallwang@reddit
How would a Windows feature update affect Macs?
Perhaps you're thinking of an outlook update instead which would be a different thread.
maggotses@reddit
No and we don't plan to in the foreseeable future. The "recall" feature is too much of a security risk.
Ihaveasmallwang@reddit
Recall is an optional feature. Just like every other optional feature, you don't need to have it enabled.
Chances are you don't even have hardware deployed that is compatible with it anyway since it's for Copilot + PCs.
DeebsTundra@reddit
Maybe I didn't read close enough, but I thought recall was only on Copilot+ PCs.
Phyxiis@reddit
I believe you can perform that via wsus and gpo or something. Was too complicated for me to understand at the time
DeebsTundra@reddit
Guess I'll have to check on my test group tomorrow. Thanks!
fastpacedsnarf@reddit
Yep, calculator will not open, windows button and search freezing.
butterbal1@reddit
Rockwell Logix design randomly going down for every user has been my biggest issue so far.
It is a large issue.
BryanP1968@reddit
We thank you for your sacrifice. I’ll be keeping everyone except a few testers on 23H2 until all this shit shakes out.
Algent@reddit
Main one I noticed on my machine is it randomly fail to open start-up programs, all of them. You logon to no teams no vpn no anything. And we started having supports calls that sounded like this could be linked.
getoutofthecity@reddit
I updated the week it came out to start testing it, haven’t had any issues.
TyloJ@reddit
Just ran into a major network issue. Many PCs with no network connection / unidentified network. Found that with this recent 24h2 update it adds WinHTTP proxy auto discover service as a dependent service for Windows Connection manager. Thus failing to start windows connection manager.. since we disabled this winhttp service via a gpo, it made things difficult. There goes 6 hours of my day.
Pub1ius@reddit
Always delay a major feature/version upgrade, at least a month or two. It's not worth the risk, as you're learning.
dollhousemassacre@reddit
24H2 update started triggering alerts in MDE for "Defence evasion tactics" at startup and shutdown.
OddWriter7199@reddit
Wow!
onefunkynote@reddit
Same thing is happening with Carbon Black. It's very annoying.
RikiWardOG@reddit
LOL dude I've seen a massive uptick in false positives lately in MDE and we have a small fleet under 200 devices
__ZOMBOY__@reddit
This is honestly hilarious
agressiv@reddit
We haven't done any upgrades, but new devices are getting 24H2, and we have about 600 so far. I've always hated upgrades, and had pretty poor experiences back in Windows 10, so I'm not looking forward to it.
With 24H2, even fresh installs, we had two problems:
We're not getting any SMB/Outlook problems, but our usage of SMB has diminished significantly since moving to OneDrive/Sharepoint Online. We use a centralized print management system, so we no longer load drivers on devices with exception of bar code label printers.
UltraLordsEg0@reddit
This is my life. The print PDF and all of our devices are acting as if they are touchscreen. Auto rotate is an option and it is defaulted to on and has been a major PITA. Even when you turn on rotation lock it unlocks itself and rotates the screen again. Even better is after the screen goes portrait you can't get it back to landscape without changing the settings manually.
MichiganJFrog76@reddit
No issues so far in the test group.
LeeTheBee86@reddit
Had storage related bitlocker from a user today. Apparently Windows told them their laptop had a new CPU installed, they restarted and got bitlockered.
BasicallyFake@reddit
I have it on two pc's and havent seen any of that
Maverick_X9@reddit
You could be having problems with the policies conflicting between SCCM and Intune. We had to go into the registry and find/delete old policies that had gotten, for lack of a better word, “stuck” in the registry files causing conflict with the new policies pushed by intune. Caused a LOT of problems with Appguard.
We started isolating the issue to the old policies because our newly imaged/Intune synced machines were working great. Maybe test your issues out on a new machine and see if they persist on it. If so, I bet you’re having similar issues .
moldyjellybean@reddit
Do you get a prize for being on the newest version first?
Why? Just bad risk management and roll out. Should not be on it or just roll it out minimal amount of users.
This has been happening for 10+ years so all that unneeded work is your own team’a decision.
Aust1mh@reddit
I’ll never understand why people rush into these updates… I test these things for weeks/months before I push slowly.
Cusack67@reddit
24H2 introduced some changes regarding SMB:
SMB signing is now required on all connections and
Guest fallback is disabled by default
https://techcommunity.microsoft.com/t5/storage-at-microsoft/accessing-a-third-party-nas-with-smb-in-windows-11-24h2-may-fail/ba-p/4154300
Also get the new ADMX template for 24H2, there are some new SMB settings in there
mc_it@reddit
I've got a handful of machines that, out of box brand new in May were getting constant OS hardlocks(*) with 23H2.
*- The computer just... stops. No error in system logs or BIOS. Screen frozen with no inputs working at all. It could be at a lock screen, at the CAD screen, or mid-workday
Since updating to 24H2, this has not occurred.
Also, the inconsistent "keyboard suddenly not working in Start menu" thing seems to be gone but I don't have 11 on my primary, and this is just going by poking at a few devices for initial testing.
ButterflyPretend2661@reddit
24h2: built by AI for AI
skipITjob@reddit
It doesn't look like anything to me...
thrownawaymane@reddit
Freeze all ~~motor~~ function pointers
ImNotPsychoticBoy@reddit
Been having similar problems, both 24H2 and 23H2
Teams fails to update and put you in an infinite death loop. Notepad and other Basic Microsoft apps not appearing after intune inplace upgrade GPO rules not getting applied
It's a mess, but we have counters against alot of the issues. Thank IT Jesus for powershell.
yeeeeeeeeeeeeah@reddit
it's almost as if doing beta testing of closed-source proprietary software for a trillion-dollar mega-corporation isn't the smartest move.
BeigeGandalf@reddit
I have a list of 5+ issues at work with 24h2. At home my gaming rig has been unstable and crashed 3 or 4 times all in different scenarios. Not impressed so far. Don't think I'd recommend for anyone needing a stable system right now.
_haha_oh_wow_@reddit
What do you use to manage your printing?
random-internetter@reddit
I upgraded my computer from 23H2 to 24H2. Two days later I advised the rest of the team to NOT do this. We will be holding off on 24H4 until these performance and stability issues are worked out.
This is the worst thing, performance wise, I've seen since Vista.
Fresh install of 24H2 doesn't seem to have these problems.
grouchy-woodcock@reddit
All M$ users are bets testers...
Fickle_Bit1481@reddit
We generally don't fully roll out Feature Updates until they are about six months old, but we aren't even giving 24H2 to our test groups anymore because of the volume of issues we're having. There's no rush, 23H2 has plenty of support left in it.
RavenWolf1@reddit
This is the way but luckily for us someone here is willing to test this out.
BirdLawyer1984@reddit
Here is a wild idea, Microsoft should test out its own software and hardware.
countryinfotech@reddit
Plenty of former MS employees have said they got rid of all of the QA forces. Now we are the QA
Its_Like_That82@reddit
I feel like they have done this with support as well. Have just enough people to mamage the ticket queue and close out tickets after people have got their solutions from Reddit.
Ok_Analysis_3454@reddit
They do- by pushing it out to you.
NeckRoFeltYa@reddit
They said they really like Crowdstrikes QA model.
Stonewalled9999@reddit
We have 24H2 on 25 low priority IT and Utility PCs. We use Cylance (not my choice) and I was rather shocked that it doesn't have issues with Cylance. I have heard some O365 apps and 24H2 incongruousness (have not seen as the live users are not on 24H2 yet)
Happy_Kale888@reddit
QA is expensive. Push it out and see what happens is free.
stufforstuff@reddit
Yup, there's always a herd of Lemmings eager to jump off the cliff so that you don't have to.
tankerkiller125real@reddit
I work in a small enough company, I'm waiting on some of the bit IT folk to report back that things are good before I even think about rolling it out. We roll out the security and bug fix updates immediately, no way am I doing that with the major feature updates though.
stufforstuff@reddit
Ah, the crowdstrike method eh?
Magic_Neil@reddit
Yeah, I’m usually pretty aggressive with rollouts, but big feature update to the masses in such a short time is.. bold.
wrootlt@reddit
We have noticed that some newer models deployed via Autopilot in some regions are getting installed with 24H2. It seems that Dell ships them with this as base image. Currently in the talk with them to get custom image for us (for a price) with Office, no crap and probably will ask to do 23H2. If it is possible. So far had to reimage a bunch the old way in one location as they needed to use some old NET app and it didn't work on 24H2. I have my old test laptop updated and a few times network went bonkers after switching it between hotspot/wi-fi/etc. Then it got stuck on reboot screen. I was thinking Netskope to blame, but saw people say CrowdStrike, which we have. Asked our security guy and he said CS say 7.19 with support for 24H2 should be out by the end of.. November? Anyway, usually we would do a very slow test with one machine here and there for months and only would plan global roll out maybe during summer. This Intune thing adding unnecessary hurdles. Btw, we don't have any feature update rings for 24H2 in Intune. And also when machines drop into domain they get WSUS policy where this update is only assigned to a test group with only my test laptop in there. We need to try to deploy one laptop here, but so far techs were saying they just deploy new laptop with Autopilot and it is right away 24H2.
secret_configuration@reddit
Thanks for beta testing for the rest of us ; ). We never rush to install the latest updates (unless there is a critical security flaw).
23H2 works perfectly fine and has plenty of life left.
Entegy@reddit
I manually updated myself with no issues so far, but I generally have a 60 day delay on feature updates.
kelembu@reddit
Crazy how bad is software getting, we are all beta testers, you have to wait at least 6 months to try a new version of something.
Maxplode@reddit
Major thing I've noticed is people complaining that Adobe takes too long to load now, and so does excel. No absolute fix other than disabling security settings, which is f-ing stupid IMO.
I had to update a graphics driver today. On this one PC though, so not entirely sure if it is coincidental. The logs aren't very helpful. But when the computer locks for longer than say 3 minutes.. the left main monitor would not come back on. Swapped the monitors and cable to test. Very strange, hopefully I don't get a call about it tomorrow haha.
taquitoburrito1@reddit
We have a custom software that's UDP heavy, it constantly fails unless the firewall is disabled. Current plan of action is keep everyone at 23H2 for a while.
79LuMoTo79@reddit
I read in this thread that most wait many months after a feature update or just bugfix and security updates(?) before deploying such a windows update?
How is it with Mac or Linux? thx.
jmbpiano@reddit
Most of our Linux machines run Debian or a descendant thereof.
We keep everything on the "stable" branch, which is designed to basically be two or three feature versions behind for most packages, but with security patches backported.
belgarion90@reddit
MacOS the conventional wisdom is wait until the .1 release to upgrade, so in this case 15.1. MacOS 15 just released and was causing a lot of problems.
alt3rn4tivity@reddit
Yeah, Defender network extension was broken and unsupported until 15.0.1. Was causing havoc with our EPM as well as VPN clients also. Hopefully 15.1 is better. Never making that mistake again on letting a x.0 patch
Wilfred_Fizzle_Bang@reddit
Zero problems here
marcoevich@reddit
We're testing 24H2 within our IT team. So far we see numerous issues with the OOBE procedure itself. It's renewed and behaves differently on different devices. Makes it hard to write proper instructions for our team.
Have some issues with print queues. They just error out for no reason without telling what the issue is.
Also some Intune filters bases on the previous Windows 11 version number needed to be changed as the version number made a jump.
No other issues found, yet..
slippery_hemorrhoids@reddit
Prod is test, duh
graywolfman@reddit
I have one work laptop with 24H2 and one with 23H2. So far the 24H2 has been solid - using it as my work daily driver. Check driver versions for updates, etc. I also have it on my personal laptop; so far, also solid.
That said, 24H2 on my personal desktop was doing BSODs so I rolled back, hah. Halo Infinite uses a version of Easy Anti-Cheat that causes BSODs with Alder Lake CPUs, and the latest update blocks the game from launching because of that issue. I was curious how bad it was.
I wouldn't roll it out to the company for another few months. The list of known issues is probably growing and none are solved per Microsoft's site..
Strange_Compote_2951@reddit
We released 24H2 to 100 machines, no issue so far.
Foofightee@reddit
I've read the 8x8 Work Desktop client is having issues with it.
https://support-portal.8x8.com/helpcenter/viewArticle.html?d=7774bf50-1c13-4b2d-9945-0cab29e22d3a
RestartRebootRetire@reddit
How hard can it be to test these releases with Microsoft's vast cloud computing resources?
Must be poor management.
tankerkiller125real@reddit
The problem isn't so much testing the actual software in the cloud (I'm willing to bet they do at least some testing in the cloud), the problem becomes all the different drivers, hardware, etc. that they can't emulate or account for in cloud installs.
RestartRebootRetire@reddit
I get that but I am curious what has changed at Microsoft to make this release so unstable.
No-Combination2020@reddit
I surprised no one has mentioned how the new windows setup fucked the unattended installation scripts.
RikiWardOG@reddit
only thing we've had so far is I had a user take 40 minutes to update
belgarion90@reddit
That's not terrible, really. Most feature updates are around 30 for us, including in-place Windows 10 to 11.
nwgat@reddit
microsoft is a small company, be considerate when talking about them, they dont have resources to fix 99% problems but our bugs aint them
Kuipyr@reddit
Breaks RCG double hop for RDS and other non-24H2 machines.
RiceeeChrispies@reddit
It pisses me off so much. They've literally had people screaming at them on Insider for months on this issue - and they just aren't arsed.
nickborowitz@reddit
We had a problem with 24H2 enabled security to block MSCHAPv2 killing our wireless districtwide. plus we are having problems with office365 mail and outlook
whoamiagaindude@reddit
Us, too. We are making a general rollback for the few machines that received the update( should not have been pushed as it was not completely tested yet). Same kind of issues you point out.
Mission-Accountant44@reddit
About 1/3 of our W11 users are on 24H2 now, only major issue I've seen is a check scanner driver had to be reinstalled.
ohyeahwell@reddit
We've been hit hard by the printing issues. Had to move people from Intune Universal Print queues to local direct queues.
mj3004@reddit
We’re running on 40 users. No issues
Dizzy_Bridge_794@reddit
I’m in no hurry to push that build.
Ochib@reddit
The only Issue we are having is the autorotation on some of the dell laptops causing issues with the rotation of the screens
muozzin@reddit
What’s up with the webview2 stuff?
aguynamedbrand@reddit
Nothing like using production systems to test major updates on.
Broad_Canary4796@reddit
Webview2 error in teams - is that just where it refuses to open at all? We were able to just repair webview in installed apps to fix that. It only happened on computer we had to use revo to remove edge since it had somehow broke and stopped updating (happened over the course of the last year though).
SMB share - have seen something on my computer but nobody else reported it, sometimes opening explorer and clicking a mapped drive causes it to freeze for a minute. Haven’t tested if it’s every time or if browsing to it by the share name is any different, this just started.
Outlook attachments - does the issue also apply to all file types in the preview pane in file explorer? We had one person get that and had to go into the registry to fix it
Smith6612@reddit
I find WebView breaks often even without a major Windows Update, simply due to Edge updating itself. Usually Reinstalling Edge fixes that, and anything related to Browser based SSO (Autodesk, Outlook attachment previews, etc).
BSODs I've heard of being an issue. I assume this has to do with drivers, and the drivers not playing too nicely with Microsoft's core isolation feature when tossed into a virtualization environment. I had trouble upgrading some systems due to Core Isolation not being compatible with some drivers installed to a few of my machines. Cleaning those old drivers out got the upgrade going, and everything has been smooth sailing.
Haven't noticed SMB problems, even with large (500,000+ item) folders. Only SMB problem I had was Microsoft changing the default SMB policy for anonymous public share browsing.
Print Queues - Had a problem with this even prior to 24H2. An old driver installed by the manufacturer that wasn't Mopria certified would print in grayscale only despite selecting color, and it used the infamously unstable WSD protocol and would regularly just not print. I switched Windows to use IPP by enabling the Enhanced Secure Printing feature on my systems. This required removing the old OEM print drivers, but has resolved all of those printing issues.
Jackofalltrades86@reddit
Anyone got ideas on how personal document encryption works in an enterprise environment e.g if said user leaves, how can you regain access to any documents covered by PDE?
Assuming the answer is Purview but not much out there yet.....
MediumFIRE@reddit
Not just you...it's buggy imo.
https://www.reddit.com/r/sysadmin/comments/1fw0eb9/windows_11_24h2_wpa3_enterprise_not_connecting/
https://www.reddit.com/r/sysadmin/comments/1fzrynm/we_couldnt_update_system_reserved_partition_error/
All things I'm overcoming, but not nearly as smooth as the last few feature updates.
CeC-P@reddit
I blocked it in our patching system the day it came out and blocked it in group policy just in case.
belgarion90@reddit
Wait, did you go to Prod with 24H2 already?
Sn00m00@reddit
nope. still on win10. LTSC till i hope 2032. nothing is broken so no need to upgrade. :)
kheldorn@reddit
We are only evaluating right now but the first issue right of the bat is quite annoying.
Installed using the release iso through SCCM/MECM the machine are UBR 1742 (September update). The October update (KB5044284) fails with error 0x800f0825.
After we install the September update (KB5043080) again (changing from UBR 1742 to .. 1742 -.-) the October update will install correctly.
Seems to me like Microsoft forgot to include the Checkpoint Update cache in the ISO ...
Doso777@reddit
AFAIR that should be fixed with the latest updates
Probably one of the known driver issues. Upgrade block is in place through Windows Update. Check why those devices even got 24H2.
Lukage@reddit
Most of these sound like application issues. Have you isolated 365 updates from OS updates?
I'll give you the SMB thing, particularly for network paths. But that's been present for all builds, not just 24H2.
AtarukA@reddit
Honestly no, no real issue here.
I do have a SMB share issue similar to yours but it's unrelated to 24h2 and happened before 24h2.
Gaijin_530@reddit
Following this one for updates.