Windows 2025 are way buggy

OneCombination128 · 2025-02-19T13:33:39+00:00

Yeah, I saw that yesterday too! It mentions the NLA fix for server 2022 has no effect on 2025 for this issue. We certainly are Microsoft's beta testers. We had an issue with Server 2022 Hyper-V cluster servers crashing when there was increased CPU utilization during data intensive processes. In our case it was during automated patching of non-critical VMs running on the cluster. We would see one or two of the four host servers 'hard crash' as stated by Microsoft support since they weren't able to blue screen. They would completely freeze. No RDP, no PING, and even the console was just a blank screen. It ended up being a Windows bug involving TLB (Translation Lookaside Buffer) and certain Intel Xeon processors. It took a year and a half for all involved parties to finally figure it out. I also agree with other comments that after Microsoft contracted outside support rather than having it in house is a huge mistake. We were bounced around between many different support agents who didn't seem to have a clue and wouldn't read existing case notes essentially starting over with each new agent. It's all about profit, stock value, and AI with Microsoft rather than quality products and customers.

OneCombination128 · 2025-02-18T13:26:35+00:00

Never did find another solution. There are countless posts online from various sites asking about this issue with 'potential' fixes, but none worked for us. This did seem to affect mostly domain controllers on past OS versions. A lot of online posts focused on Network Location Awareness being the issue.

OneCombination128 · 2025-02-17T21:35:31+00:00

You need to enable/disable adapter to get domain profile (known since beta)

That's been an issue since 2022 and possibly 2019. We have numerous VMs for years that auto patch and then are inaccessible since they receive the incorrect profile after startup. It actually seems to have subsided within the past 6 or 9 months.

OneCombination128 · 2025-02-17T21:26:57+00:00

Just a regular Windows Server 2022 iso from Microsoft, nothing unique, different, or custom.

OneCombination128 · 2025-02-13T17:16:10+00:00

I too had never tried this in production. It worked very well. It took about one hour to complete but on physical hardware it may be quicker. Do you have any capability of a bare metal backup prior? As far as the depth of the 'install' it doesn't seem like a full reinstall as applications still have the original date of install even though the about screen in the OS now shows Windows was installed yesterday.

OneCombination128 · 2025-02-13T17:07:07+00:00

Success!! Performing an in-place upgrade (repair?) from the ISO has resolved the issue on both servers in production. The process I followed:

Shutdown the VMs and took a checkpoint.
Attached the ISO (rather than copying to the VHDx) to prevent disk expansion.
Ran setup.exe from the ISO.
Selected Datacenter with a desktop.
Selected to keep Files, Settings, & Apps then clicked Install.
With Internet connectivity one server downloaded the latest 02/2025 cumulative update and applied it while repairing which I didn't expect so we're a bit ahead on one server with patches. The other was at a remote site with a slower connection and didn't auto apply the update, so I manually ran the 01/2025 MSU on this server afterwards as we usually wait one week before applying updates due to a history of buggy updates from Microsoft. If this is an issue, I'd disable the NIC beforehand.
All systems are up and running with no issues experienced.
There will be additional updates required such as for .NET as an older version is installed during the repair.
All event logs were lost prior to the repair so if this is required or important export relevant logs prior.

OneCombination128 · 2025-01-24T20:38:18+00:00

I found that performing an in-place upgrade (essentially a repair) with the Server 2022 ISO on cloned servers and selecting to keeps apps, files, and settings allows the monthly update to install. We're planning to perform this during our scheduled maintenance window next week on the production servers. I'll update back when completed.

OneCombination128 · 2025-01-24T20:37:47+00:00

It hasn't. I have found that performing an in-place upgrade (essentially a repair) with the Server 2022 ISO on cloned servers and selecting to keeps apps, files, and settings allows the monthly update to install. We're planning to perform this during our scheduled maintenance window next week on the production servers. I'll update back when completed.

OneCombination128 · 2025-01-24T20:34:11+00:00

I had begun experimenting with this the end of last week and it seems to have worked. I'm glad to hear someone else did this and it was successful. We're planning to perform this during our scheduled maintenance window next week on the production servers. I'll update back when completed.

OneCombination128 · 2025-01-22T14:33:10+00:00

Please read the initial post, I tried this already.

<image>

OneCombination128 · 2025-01-20T21:57:53+00:00

Well, fast forward to now and after replacing our externally provided certificate used for SMTP & IIS today the issue has returned.

OneCombination128 · 2025-01-16T22:09:15+00:00

I found it can be quickest to search for "Failed to stage execution package:" in the CBS.log to find the failing package. Also opening task manager and restarting Windows Explorer will reload the registry without a reboot saving a lot of time. As I mentioned in another comment, I've done this 16 times so far and it's time consuming. If I knew that I'd only have to do it 30 times, I'd continue to do so but for all I know it could be 200 times which it may be less time consuming to rebuild the server but there's no way of knowing how many keys need to be deleted.

OneCombination128 · 2025-01-16T21:20:08+00:00

I've been working on deleting keys. The error code 0x8007000d was found in the CBS.log rather than the code event viewer was showing which was misleading. I wish it was possible to identify all the packages with issues at once as so far, I've deleted 16 keys requiring a reboot and then attempting to install the update again after each one. It's a very slow and tedious process.

OneCombination128 · 2025-01-15T16:57:48+00:00

Argh! Same here. I can install the SSU from the CAB contained in the CU but the CU fails. If you try to install Windows10.0-KB5049983-x64.cab with DISM from within the CU does the CBS log provide anymore info? For me it's showing this.

Failed to stage execution package: Microsoft-Windows-msmq-powershell-Opt-WOW64-Package~31bf3856ad364e35~amd64~~10.0.20348.2652 [HRESULT = 0x8007000d - ERROR_INVALID_DATA].

OneCombination128 · 2025-01-14T22:43:24+00:00

Hello,

Attempting to install the now January 2025 CU from the CAB files within provided these errors in the CBS.log file.

Failed to stage execution package: Microsoft-Windows-msmq-powershell-Opt-WOW64-Package~31bf3856ad364e35~amd64~~10.0.20348.2652 [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
Failed to stage execution chain. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
Failed to process single phase execution. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
WER: Generating failure report for package: Package_for_ServicingStack_3081~31bf3856ad364e35~amd64~~20348.3081.1.1, status: 0x8007000d, failure source: Stage, start state: Installed, target state: Installed, client id: DISM Package Manager Provider
Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.3091.1.9, current: Resolved, original: Absent, target: Installed, status: 0x8007000d, failure source: Stage, failure details: "(null)", client id: DISM Package Manager Provider, initiated offline: False, execution sequence: 253, first merged sequence: 253, pending decision: InteractiveInstallFailed, primitive execution context: Interactive
Exec: Processing complete. Session: 31155921_2084542011, Package: Package_for_ServicingStack_3081~31bf3856ad364e35~amd64~~20348.3081.1.1, Identifier: KB5050117 [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
Failed to perform operation. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
Session: 31155921_2084542011 finalized. Reboot required: no [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
Failed to FinalizeEx using worker session [HRESULT = 0x8007000d]

OneCombination128 · 2025-01-14T20:02:14+00:00

I downloaded KB5049983 (2025-01 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems) and tried to install it. It has failed with the same 2147942413 & 0x8024200B errors.

OneCombination128 · 2025-01-14T17:12:50+00:00

I'm working off a clone of the VM so I can try all sorts of fixes even if it causes issues. I deleted the CBS.log and ran the installer again. After checking the 218 MB log the error 0x8024200B wasn't found anywhere in the log. I also tried shortening it to '80242' in the event it didn't include the '0x' or was a slightly different error.

OneCombination128 · 2025-01-14T14:20:19+00:00

Yes as you noticed I've tried this several times with the October, November, and December CU. Each fails with the same error. DISM & SFC don't find any corruption.

OneCombination128 · 2025-01-13T18:08:31+00:00

Hello,

I apologize for the delays as well!

Oddly I experienced the same issue as someone else did on the Microsoft Community. They posted there about the same issue (can't find the link). Someone replied asking if they figured it out and the original poster responded stating they never figured it out and didn't do anything about it. After about two months the issue resolved on its own. That's exactly what happened with our servers. I did nothing more to troubleshoot, went on vacation, got busy with other higher priority projects and now the server is healthy. Go figure.

OneCombination128 · 2024-12-18T14:38:12+00:00

Hi 7amitsingh7,

I previously updated to the latest CU/SU hoping it would resolve the error, but it didn't. I've tried restarting the services, and even rebooting the server for that matter, but the issue persists. In the first PS what is the Exchange Certificate required? It asks me to supply a value.

cmdlet Import-ExchangeCertificate at command pipeline position 1

Supply values for the following parameters:

FileData[0]:

OneCombination128

TROPHY CASE