Forum Widgets
Latest Discussions
WMI Filter for non-Hyper-V Host
I have been struggling for several days trying to set a GPO WMI Filter that would apply settings to any server, virtual or physical, as long as it is not the Hyper-V Host. It should apply to any VM on VMWare or on Hyper-V hypervisors. I found many suggestions online but none of them really work, like looking for Hypervisorpresent, that is also set to TRUE on VMs so no help. I have many ways to find and apply to an Hyper-V but EXCLUDING Hyper-Vs seems to be a tough one, the WMI filters are designed to find something and apply if it finds it, not the opposite. I have tried queries on the OptionalFeatures class, again it helps me find the Hyper-V but not EXCLUDE it. Anyone have an idea about doing this. BTW, this is to apply a setting only to non-Hyper-V and ignore if it is an Hyper-V. I am also trying to avoid blocking GPOs at a specific OU and re-linking all but 1 GPO from that level, I have to assume that there is a way to target all servers except Hyper-V. Hopefully someone has succeeded in doing the same. Thank youSolvedPepeLePewFeb 21, 2026Copper Contributor51Views0likes3Comments
0x000003eb Windows cannot connect to the printer.
Hello fellow Windows administrators, I have installed Windows 2025 as a print server. I share Xerox network printers from there using the Xerox Gobal PostScript driver (requirement). When installing the shared printer from that server (\\2025server\ double-click the printer), file C:\Windows\system32\spool\DRIVERS\x64\3\PS5UI.DLL gets overwritten by the version from the server (a newer version 2026-02-11 that was pushed by monthly windows updates) which comes from "\\2025server\print$\x64\PCC\ntprint.inf_amd64_c9d56d0edd975df6.cab". It overwrites the version actually in the local server before the printer installation completes. This is normal behavior. On windows 2016 and 2019 the printer installation then fails with error "0x000003eb Windows cannot connect to the printer" and 2 eventlogs : "The print spooler failed to import the printer driver that was downloaded from "\\2025server\print$\x64\PCC\ntprint.inf_amd64_c9d56d0edd975df6.cab" into the driver store for driver Xerox Global Print Driver PS. Error code = 800702e4. This can occur if there is a problem with the driver or the digital signature of the driver." And : "The print spooler failed to load a plug-in module C:\Windows\system32\spool\DRIVERS\x64\3\PS5UI.DLL, error code 0x8007007F. See the event user data for context information." If I install the the exact same shared printer on any other OS than 2016/2019 servers , local Ps5ui.dll gets overwritten with the server 2025 (2026-02-11) version and printer installs and fine. I figured that if I go to my old print server (2022) and retrieve ps5ui.dll from there, put it in local folder on the 2016-2019 servers (overwriting the 2026-01-14 | 2026-02-11 version) and install the shared printer again, now it installs fine. (It does not retreive ps5ui.dll from the 2025 again and so it does not overwrite the local onel). I even re-installed 2025 in a vm without network (so no windows update) and extracted ps5ui.dll from there, and this one works too. This issue seems to be caused by recent windows update, the first culprit I'm aware of is dated 2026-01-14. The february update installed today also modifies ps5ui.dll on the 2025 server, but does not resolve the issue either. So, either there's something I have to change on the 2016/2019 servers, or there is a bug in that file… I'm thinking the later as the original file form the 2025 iso works fine. :\Solvedqm2Feb 11, 2026Copper Contributor226Views0likes2CommentsTurning Off Tamper Protection on Workstations
How do I turn off Tamper Protection on a domain-joined Windows 11 workstation? The problem is a workstation has Windows Defender in Passive Mode instead of being in Not Running mode after installing a 3rd party antivirus. Windows Defender is making running network applications from the servers much slower because it's still real-time scanning. I also suspect Tamper Protection is also preventing network drive exclusions from working on this workstation and on the ones that use Windows Defender without a 3rd party antivirus. I've tried adding every registry entry, Group Policy, and PowerShell command on the local workstation I could find to disable Windows Defender, but nothing works. I'm assuming this is due to Tamper Protection ignoring everything? This is an on-premises domain and doesn't use Microsoft Intune or Microsoft Endpoint Configuration Manager.SolvedDavid OwensDec 24, 2025Copper Contributor318Views0likes2Comments
WINGET is not recognized as a commandlet on win 2k19 server fresh setup
I have setup a new win2k19, I followed the instructions Install-PackageProvider -Name NuGet -Force | Out-Null Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery | Out-Null Repair-WinGetPackageManager When I try anu winget command I get winget is not recognized as a commandletSolvedSalam_ELIASNov 29, 2025Brass Contributor182Views0likes2Comments
Certificate authentication with SID not working
When trying to login to Windows (against AD) using a certificate with the SID extension present in the certificate, it will not work if the SAN UPN is missing in the certificate. The error message "Your credentials could not be verified" will be displayed. Changing the certificate template to include SAN UPN will make the login work as expected. Is it by design?SolvedJan LiikamaaOct 28, 2025Copper Contributor199Views0likes2Comments
2025-10 Cumulative Update for Windows Server 2019 (KB5066586) Undoes Update on Reboot
We have a Windows Server 2019 Standard which will not install the 2025-10 Cumulative Update for Windows Server 2019 (KB5066586) update. The installation part goes fine, but when the server is rebooted to finalize the update, it goes into "Undoing changes". Then it reboots again, and I am back where I started. The error code is 0x8007000d. I have done the following to debug this: Ran System File Checker sfc /scannow. No errors found. DISM /Online /Cleanup-Image /ScanHealth. No errors found. Ran Windows Update Troubleshooter. No errors found. Shut down Windows Update services. Renamed SoftwareDistribution and Catroot2 folders. Restarted services. No change. Ran ScanDisk. No errors found. Disabled antivirus. No change. Ran Disk Cleanup and manually deleted additional temp files. No change. Checked Event Viewer. Only error is Event 20 which is a failure of the Windows Update Agent. I am out of ideas. If anyone has some, I would much appreciate the help. I am out of ideas.Solved1.6KViews0likes10Comments
Replacing our Server 2016 RDS with Server 2022 RDS
Hi All, I have a Server 2016 terminal server. I set it up a while ago obviously, and I have 10 2016 RDS CALS installed in the RD license manager. We are part of a domain, and I have a group policy assigned to our current RDS server with lots of user options like session limit, printer redirection, max profile size, etc. I created a new Server 2022 VM and installed the RDS role and all it's features. But for some reason, it doesn't appear to be configuring the services. I add the roles via Server Manager once installed, the computer reboots when the server comes back up, Server Manager starts and says the install is complete. But when I go to the Remote Desktop services section in Server Manager, I get this message: "A remote Desktop Service deployment does not exist in the server pool. To create a deployment, run the Add Roles and features wizard and select the Remote Desktop Services installation option." From looking around on the Internet, at step 3. there should be a configuration step where Server Manager starts and configures the RD gateway, license manager, etc. I also found some articles on the Internet about disabling IPv6 or making sure the server is a member of a domain. I've already tried those things and it's still not helping. I also removed all the Roles and readded, but it still behaves the same. The configuration step doesn't start on reboot and no RDS server. I also installed a web certificate and installed it on the server from my CA. Is there a better way to do this? I haven't worked with RDS in a long time. Here's some event viewer messages Event ID 1306 Remote Desktop Connection Broker Client failed to redirect the user domain\administrator. Error: NULL Event 102 The Remote Desktop Gateway service requires a valid Secure Sockets Layer (SSL) certificate to accept connections. Ensure that you have obtained a valid SSL certificate, and then bind (map) the certificate by using RD Gateway Manager. For more information, see "Obtain a certificate for the RD Gateway server" in the RD Gateway Help. The following error occurred: "259" Event ID 2056 The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database. Pooled virtual desktop collection name: NULL Error: Logon to the database failed. Event ID 85 The Remote Desktop license server could not be registered as a service connection point in Active Directory Domain Services (AD DS). Ensure that there is network connectivity between the license server and AD DS. To register the license server as a service connection point in AD DS, use Review Configuration in the RD Licensing Manager tool.SolvedralvarezOESOct 09, 2025Copper Contributor527Views0likes2CommentsUpdating PowerShell5 via WSUS - possible and needed?
Good day, not sure if its the right subforum. If not, please move. I have a couple of 2016 servers in a domain where I handle updates via WSUS. On the WSUS, in the tab Products and Classifications, PowerShell - x64 is check marked but PowerShell Preview - x64 is not. I guess this refers to PowerShell 7 and it works on the servers on which PowerShell 7 is installed. But the PowerShell 5 versions are not updated via WSUS. The PSVersion on some servers show PSVersion 5.1.14393.8062 which is not the most current. Is there a way to update PowerShell 5 via WSUS, how's the Product named in the tab Products and Classifications? Is it possible to update PowerShell 5 via WSUS at all ?Is there a need to update it at all? Best RegardsSolvedhauer94Aug 12, 2025Copper Contributor148Views0likes1Comment
Wireless secure Windows server 2022
Hello everyone, I am trying to implement ‘wireless secure’ in my domain. I have followed various guides and everything seems to be configured correctly, but I keep getting this error: Reason: Explicit EAP error received Error: 0x40420016 EAP reason: 0x40420016 EAP root cause string: Network authentication failed\nThe authentication method required to connect to the network is not available in Windows. EAP error: 0x40420016 I have verified that communication via AP-WLC-NPS is working correctly, but it is unable to authenticate via eap-tls. Do you have any suggestions? I have collected several logs, but many of them may not be necessary. Thank you for your support.Solvedfranga92Aug 11, 2025Copper Contributor151Views0likes1Comment
Tags
- windows server2,250 Topics
- Active Directory840 Topics
- management392 Topics
- Hyper-V343 Topics
- networking329 Topics
- security295 Topics
- storage217 Topics
- clustering158 Topics
- powershell150 Topics
- AMA102 Topics