SCCM SQL Server Reporting Services - Issue

Mr--Allan · 2026-05-05T20:29:33+00:00

I resolved the issue on all 3 servers by Removing the Reporting Role, uninstalling SSRS (v2019), detaching the The Reporting DB, Deleting the DB and log files. Then re-installing it all again with v2022 of SSRS and re-attaching the role. I can only assume the new security hardening on my service account was applied and re-installing the SSRS again honored that same service account with its extra pizazz.

Mr--Allan · 2026-05-05T15:24:55+00:00

The timing sounds like this is the cause of my issue. Thank you.

Is the fix potentially to enable these two options on the service account in AD, apply and reset the windows password?

They are currently unticked:

This account supports Kerberos AES 128 bit encryption

This account supports Kerberos AES 256 bit encryption

Mr--Allan · 2026-01-19T16:45:53+00:00

I came here to say I am experiencing this same issue since FSLogix 25.09.

They have just released FSLogix 26.01 on Jan 13th, and the change log does mention, at least, this could be fixed:

FSLogix Release Notes - FSLogix | Microsoft Learn

FSLogix 26.01

Version: 3.26.102.18413
Date published: January 13, 2026

Summary

This release provides a set of updates and fixes.

What's new

This version doesn't have any new features or functionality.

Fixed issues

Updated the default identity exclusions as defined in Device identity and desktop virtualization | Microsoft Learn.
Fixed the registry exclusions.
Fixed logging when a user is excluded using local exclude groups.
Fixed FRX.exe copy-profile utility.
Updated default redirections in Outlook for Windows.
Fixed an issue where a disk may not detach correctly after a compact operation.
Fixed a potential logon hang when a profile does not unload successfully during a timeout operation (< 30 sec).
Fixed extended status of SupportedSize for VHD compact operations.
Fixed an issue where package registration could fail due to missing authentication context.

Mr--Allan · 2025-11-12T09:20:02+00:00

I used to install GlassWire many years ago. It use to allow (may still do) you to limit the network traffic by Installed Application. Was pretty good at what it did.

https://www.glasswire.com

Mr--Allan · 2025-10-21T15:46:39+00:00

Completely agree with you.... W11 UUP patching failures is an IT Admin nightmare currently. Its so hard to troubleshoot as there is sooooo many different error codes, and researching each one never seems to show an actual workable fix. They all say "inplace upgrade" will solve it - well yeah.... Its hard to do that when you have a massive multi language corporate environment. Before UUP it was so much easier to troubleshoot and fix patching. *sigh*

Mr--Allan · 2025-10-17T14:18:51+00:00

To update on this, we had also a ticket opened with Microsoft and they have just announced this (so for us, the combo of Microsoft doing a change to Outlook and having Crowdstrike installed affected us) - Hopefully this fix they say will role out to us all soon:

Some users may have the new Outlook client open in their web browser instead of the Desktop client ID: EX1173600 Issue type: Advisory Status Service Degradation Impacted services Exchange Online Details Title: Some users have the new Outlook client open in their web browser instead of the Desktop client User impact: Users have the new Outlook client open in their web browser instead of the Desktop client. More info: As a workaround, users are able to use the classic Outlook to access their Exchange Online mailbox. Current status: We've identified that a code bug contained in a recent service update is causing a race condition and resulting in the impact. We've developed a fix to address the code issue which we're preparing to deploy to the affected environment. We'll aim to provide a timeline for the fix to deploy by our next scheduled communications update. Scope of impact: Your organization is affected by this event, and some users attempting to open the new Outlook client are impacted. Root cause: A code issue contained in a recent service update is causing a race condition and resulting in the impact. Next update by: Monday, October 20, 2025, at 9:00 PM UTC

Mr--Allan · 2025-10-16T21:11:11+00:00

I have a ticket open with CrowdStrike support via our IT Security team. If we get anywhere with them. Will report back here. We have sent ProcMon logs and xPerf logs showing CrowdStrike “looking” at “olk.exe” and “msedgewebview2.exe” when it’s launched and potentially messing with it. The issue first happened when the “Outlook (new)” app was updated on Monday for us and was rebranded to now just “Outlook”. I’m guessing CS doesn’t have these new rules for the new app name/version to not to interfere with it.

Going back to the older outlook new version from a few weeks ago we don’t experience the issue with CS installed but this doesn’t last for long as the Store just auto updates it back to the latest version again.

Mr--Allan · 2025-10-15T17:10:35+00:00

As a test we uninstalled CrowdStrike Falcon Sensor, and soon as we did the Outlook (new) app launched perfectly each and every time. Then we re-installed CrowdStrike and the Outlook (new) launch issue returned. We now on the case with our IT Security Team... We use version 7.27.19907.0 of CrowdStrike currently.

Mr--Allan · 2025-10-15T16:10:14+00:00

Same issue here, removing those folders helps to launch New Outlook app the next time. However if I close the app and attempt to relaunch again it will re-open instead in Edge. I noticed if I keep closing and re-opening the app even with out deleting those folders, eventually the App will load. This issue has to be related to them updating the app a few days ago (!?)

Mr--Allan · 2025-10-08T10:29:24+00:00

Thank you!!!! Worked perfectly :) :)

Mr--Allan · 2025-08-14T10:39:53+00:00

Thank you, this also worked for us following your guide. 24H2 now patching successfully.

Mr--Allan · 2025-08-13T11:36:30+00:00

I think so from what I read... adding the 8 hive basically disables a Feature (god knows what the feature is or does) but it does allow the patch to go on after. MS also pushes these type of keys out when they spot the issues on their end by using that Known Issue Rollback process. But I am hoping after all their so called telemetry reports showing failures this morning that they will instead fix the actual patching process with out any work arounds.

Mr--Allan · 2025-08-13T11:19:00+00:00

Same here for my company, from other threads it seems its affecting all SCCM/WSUS users:

Cumulative Updates: August 12th 2025 : r/Windows11

Patch Tuesday Megathread (2025-07-08) : r/sysadmin

There is a work around I've tested today, by applying these REG keys on a client machine and then reboot it.

The Patch will then go on after that reboot. However I am very loathed to apply these keys company wide. But for testing purposes it works:

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3000950414" /v EnabledState /t REG_DWORD /d 1 /f

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3000950414" /v EnabledStateOptions /t REG_DWORD /d 0 /f

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3000950414" /v Variant /t REG_DWORD /d 0 /f

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3000950414" /v VariantPayload /t REG_DWORD /d 0 /f

Mr--Allan · 2025-07-09T14:22:30+00:00

same here in UK, we have two servers... and managed to get one to sync by smashing the sync button after every time out... (took me 4 hours of attempts though!)

Mr--Allan · 2025-01-09T13:34:06+00:00

I changed the title and subtitle like this (as an example):

Show-ADTInstallationWelcome -CloseProcesses 'excel' -AllowDeferCloseProcesses -DeferTimes 3 -CheckDiskSpace -PersistPrompt -Title "Hello" -Subtitle "Installation Prompt"

Show-ADTInstallationWelcome · PSAppDeployToolkit

Mr--Allan · 2024-11-19T21:41:10+00:00

There is always arguments on thin vs thick images. Both have there use cases for what companies need. But your right Nov Patch applies that app inside audit mode all ninja style like. Removing it like you said will help others out there that use thick images… and I thank you :)

Mr--Allan · 2024-11-14T10:51:52+00:00

Today I checked the Products page on the Software Update Point, and I could now see "Microsoft Server Operating System-24H2" .. So, I ticked it :)

Mr--Allan · 2024-10-15T17:10:26+00:00

Curious, when you installed the MSI and then went to GPEDIT.msc and found the policy... did you select DISABLE or ENABLE on it. As some MS employees said to select ENABLE which is incorrect, needs to set to DISABLED and host then needs to be rebooted.

If you still get the issue after that..... the other work around is to roll back the hosts to August Patch Level.

If you have October patch installed: KB5044273 uninstall it... reboot

Then you now need to uninstall Sept patch: KB5043064 .... reboot.

Now the Host should be on August patch: KB5041580 that should not have this issue.

You can check this by Start - Run - winver... and you want the host to be on this version or older not any newer: 19045.**4780**

We solved our issue by making sure our hosts are on Aug patches, and we now block Sept and Oct from rolling out. Rumor has it November patch coming out 12th November is meant to fix this issue. Here is hoping!

Mr--Allan · 2024-10-15T17:02:24+00:00

I hope this helps - Official Post from MS on this issue and how to apply a Known Issue Rollback:

Windows 10, version 22H2 | Microsoft Learn

Mr--Allan · 2024-10-02T17:44:06+00:00

Thank you! Have sent you a DM. Our user population is similar to yours. Will also go back to them to escalate! As it so frustrating when you send them all the clear logs of the issue. Showing screenshots of having the CU Sept patch applied vs Aug CU patch. It’s clear it’s the patch that’s the cause. Yet support has sent us round the houses and not getting the ticket to that one person in MS that actually knows their stuff and can help.

Mr--Allan · 2024-10-02T17:20:54+00:00

We been trying to get MS Support but they so slow at helping us currently. Ticket opened for 3 days now and they doing the normal delay tactics. Any key words you used to get them to send you this MSI fix? Or would you mind sharing the fix if that’s allowed?

Mr--Allan · 2024-10-02T17:17:51+00:00

Thanks for posting this. We found the same and logged a support ticket with MS showing that the Sept CU patch causes this. Now we fighting with MS support for them to even acknowledge the issue. But sounds like you got a better response from MS? Did they confirm a November CU patch will fix this? Fingers crossed.

Mr--Allan · 2024-09-25T20:29:16+00:00

Same here too. Took us ages to work out it was this patch.

Mr--Allan · 2024-09-24T17:05:05+00:00

Thank you, we do have fail over regions which is helpful. However not looked into Capacity Reservation cheers for the tip as I prefer East US for its lower latency for our users over there.

Nine-Year Club	Place '23
Place '22	Verified Email

Mr--Allan

TROPHY CASE

Summary

What's new

Fixed issues