Server 2022 - errors 0x8007000d, 0x800f0922 during updates and 0x800f0922 when uninstalling roles
Hello, I'm experiencing persistent update issues on a Windows Server 2022 (21H2, build 20348.3207). The problem started immediately after installing the latest Servicing Stack Update (SSU build 20348.3320). Since then, I'm consistently receiving these errors: 0x8007000d when performing Windows Update. 0x800f0922 during installation of cumulative updates. I have already attempted extensive troubleshooting, including: Resetting Windows Update components (SoftwareDistribution, catroot2 folders) Running DISM /Online /Cleanup-image /RestoreHealth and sfc /scannow (both complete successfully without finding errors) Attempting manual installation of updates Clearing and verifying the component store Checking registry entries and group policy settings Verifying date/time settings Attempting an in-place upgrade from ISO (which also fails) None of the above steps have resolved the issue. Additionally, the installed SSU (build 20348.3320) cannot be removed manually. Could someone please assist or provide guidance on further diagnostics or solutions? Thank you very much in advance!
Windows Server 2019 and .NET 4.8?
Hello, On a fully updated Windows Server 2019, roles and features allow me to install only .NET 4.7. One of the solution we are using require .NET 4.8 (Adaxes). When I install .NET 4.8 using the installer available here https://support.microsoft.com/en-us/topic/microsoft-net-framework-4-8-offline-installer-for-windows-9d23f658-3b97-68ab-d013-aa3c3e7495e0 It works, I can install Adaxes, but it break ServerManager as well as Azure AD Connect. What's the correct procedure to install .NET 4.8 on Server 2019 without breaking anything else? Thanks a lot
WS2025 - LocalKDC Service Stopped
I have found that this service was disabled before the December update, for some reason it has gone to automatic and cannot be started, maybe this behavior is normal if you are not using this feature. After the January security patch the service still does not start, I think microsoft should report this problem. This problem occurs in a clean installation without any role installed or configured. If you try to start the service it shows the following error
Conflicting entries in dfsr schema preventing migration from frs to dfsr
Hello, I am having issues converting from frs to dfsr in a domain with 10 domain controllers a mix of 2012r2 and 2016 domain controllers ForestMode : Windows2012R2Forest DomainMode : Windows2012R2Domain Schema version 88 In the initial phase dfsrmig /setglobalstate 1 the sysvol suscription should be created but it fails with a error 87 syntax incorrect. I have check dfsr through dfs management and if I select add replication group to display the below is the error There are no replication groups in this domain. The Active Directory Domain Services schema must be extended before a replication group can be added to this domain. If i manually attempt to create a replication group I get the message below The active directory domain service schema on domain controller xxxxxx cannot be read. This error might be caused by a schema that has not been extended or was extened improperly, An attribute schema object cannot be found. even in powershell if I run get-dfsreplicationgroup -groupname * The Active Directory DomainServices Schema on domain controller xxxxxx cannot be read. I checked the schema entries using adsi edit and there a multiple cn=ms-dfsr entries that have cnf(guid) after the cn-ms-dfsr entries. I have attempted to move the schema master role but have not had any success. I have searched every forum I can find and it looks like schema entries are permanent once they are put in place. I have even opened a support ticket with microsoft support TrackingID#2503070040000116 and they have worked with me once and completely stopped responding. My current next steps are to remove all domain controllers except for the one holding the fsmo roles in hopes possibly the schema cnf will clear or if they don't I can take snapshots/checkpoints and attempt to add the correct missing schema entries that are currently appended with the cnf(guid). I figure this way I can make a change and roll back the one domain controller to the snapshot checkpoint. Eventhough I have found some forums and articles that indicate that you can remove schema entries from the schema partition using adsi edit it isn't possible on any server os newer than 2000 server. Any guidance and recommedations that can be provided would be greatly appreciated. I have really been let down by official microsoft support as they have ignored any contact and emails after a initial working session when they had me set the domain naming contect system global settings msflags to 0 which did nothing to resolve the issue and they have avoided providing any support since then..Net Core IIS App runs on Server 2016, not on Server 2022
We have an IIS App, a .Net Core application that runs fine on Server 2016. We have .Net framework 4.8 on both servers, IIS 10 on both servers and .Net Core 6.0. What happens on Server 2022 is that we receive an error that says can't reach this page in the browser. We have checked windows firewall rules, event logs, IIS logs and are stuck on this. Any suggestions are appreciated.Edit subnet mask or scope in dhcp server running in windows server - Solved
it's not possible to directly change the subnet mask of an existing DHCP scope in a running Windows DHCP server. Here are the steps: 1. Export the Existing Scope Configuration: Open a command prompt with administrative privileges. Type the following command to export the scope configuration to a text file: netsh dhcp server \\<DHCP_Server_Name> scope <Scope_IP_Address> dump > C:\dhcp.txt 2. Modify the Configuration File: Open the dhcp.txt file in a text editor. Locate the line that specifies the subnet mask (e.g., SubnetMask 255.255.255.0). Change the subnet mask to the desired value. Save the changes to the file. 3. Delete the Old Scope: In the DHCP management console, right-click the scope you want to modify and select "Delete." 4. Import the New Scope: In the command prompt, type the following command to import the modified configuration: netsh exec c:\dhcp.txt 5. Verify the Changes: In the DHCP management console, check if the scope has been re-created with the new subnet mask. Right-click the scope and select "Properties" to confirm the subnet mask change. (Major Point - Ensure that your existing network address and subnet network address remain the same after making changes. If they are not the same, you need to modify the entire network address in the text file. For example, if the original subnet is 255.255.255.0 and the network address is 10.1.10.0, and you change it to 255.255.252.0, then the network address should also be updated to 10.1.8.0. Therefore, you must replace all instances of 10.1.10.0 with 10.1.8.0 in the entire text file (using Ctrl+H for the replacement). Thats it....BLOG: Guidance for Windows Recovery partition (WinRE) patching and why you would need it
This is an extended blog, which continues in comments. Windows Client and Server should have this WinRE Partition. You want to enlarge the C (OS Partition) in a VM and WinRE partition is in the way. The most common advice is to delete the WinRE partition. And this is a bad advice imho. The WinRE partition enables you for different to access different options including uninstalling Updates *pre-boot* that prevent a system startup. This doesn't happen very often but it can happen. This feature has been added to WinRE starting with Windows Server 2022, and Windows 10 22H2 / Windows 11 22H2, or newer. It is quite unknown, though. You can do more like direct UEFI access, and troubleshooting GPT / UEFI required and recommended anyway for both Windows Server and Client. Proper location and number of WinRE partitions on a physical disk 1. WinRE should located right hand side to the C partition If you find that your WinRE it is located left of the OS boot drive (C) it has been installed by a bugged release (old ISO). I am sure it was Windows Server 2019 when we noticed that. Aka Windows 10 1809. See below why the certainty. When installing Windows or especially Windows Server always use the lastest ISO for fixes like this or for in-place upgrades. There is no such updated ISO for Windows Server 2016, very unfortunately. They started patching them on a monthly basis with Windows Server 2019. You can access your latest ISOs either via my.visualstudio.com (Dev / Test use only), or admin.microsoft.com for VLSC or CSP production use. 2. There could be more than two WinRE partitions to the right hand side of the C partition This often happened when the existing could not be enlarged during in-place upgrade. Maybe also a Bug. Haven't seen this long time. It was common before Windows 10 1809. It is common though if you are using more than one Windows Installation on one physical disk. This is known as side-by-side installation or more commonly "Windows OS multi-boot". Each OS will create and maintain its own WinRE Partition (by design). Multi-boot is common for people that use designated Windows Installation for specific use cases, like Windows Insiders to test different Insider branches on one physical machine and disk. More information can be found in the comment below. Patching Windows RE is important There is a 2024 CVE that needs to addressed. Please find more information in the comments below on the "How-to".patching the WinRE CVE and remediate the 01-2024 LCU failing. More information on how to actually fix this can be found in this comment below Relocate WinRE partition A WinRE Partition left of C (OS Partition) makes no sense as Windows still may not move partitions to the right or left (while technical possible). Windows can only shrink Partitions As such I don't get how one can at all shrink C (to the right only). Mind that if you change / delete WinRE partitions you need to inform Windows about it via reagentc.exe These are tools you have at hands: Windows Diskpart Settings App > Storage Settings > Advanced Storage Settings > Disks and Volumes Windows 10 22H2 / Windows 11 22H2 / Windows Server 2022 or newer. diskmgr.mmc all legacy OS Windows Key + X > Disk Management Trusted 3rd party tool for Home Use (Windows 10 / 11) or paid for Windows Server use: Minitools Partition Wizard (Free) Formerly recommended Minitools Partition Wizard but they now have a paywall. If you are ok I would still recommend it. These can do everything! Acronis Partition Wizard isn't nice too old code and slow. Not optimized for SSD / NVMe. Both recommendable tools are available through winget. Bonus: Use Paritioning tools for Windows Server / Expanding WinRE / Resize OS Drive Create a PAWS VM Client or Server on Azure Stack HCI, Azure, Hyper-V, VMware etc. Buy the Tool (aquire a license, required for Windows Server) Install the license on the PAWS Shutdown affected VM Attach affected virtual disk to the PAWS VM, do the resize job Attach modified disks back to the original VM Pro: easy and licensing costs savyy Cons: Downtime and manual task Hope this is helpful to you. Appreciate your likes, spreading the word.
MICROSOFT XPS DOCUMENT WRITER
Good Day! Does anyone know who to install the same MICROSOFT XPS DOCUMENT WRITER that installs on WINDOWS 10/11 on SERVER 2025. An application needs it to send emails with attachments via OUTLOOK. None of the drivers available to install manually are the same as the one on WINDOWS 10/11. Thank you!
