Recent Discussions
Groups and roles issues
Hello, We use two user accounts, one that is a server administrator and that we use to connect to the servers via RDP (ADMaccounts). The other is not an administrator and we use it on our workstations (USRaccounts). I deleted from Gateway Users the Builtin\users group because I don't want users to access even though they can't do anything. For now I added another group as Gateway Users with our USR accounts. ADM accounts are member of Gateway Administrators. When Im logged into WAC with the ADM user and access to WAC, the browser asks me for credentials, I enter the ADM credentials, and I log in. When I am at my workstation, I access the URL and log in without being asked for credentials with the USR account session. I do not understand this behavior. I need to access from my workstation with the ADM account. How can I make the browser ask me for credentials? Do I have to open the browser with the admin credentials every time I want to manage WAC? Thanks, Best regards
CSV Auto-Pause on Windows Server 2025 Hyper-V Cluster
Hi everyone, i'm facing a very strange behavior with a newly created HyperV Clsuter running on Windows Server 2025. One of the two nodes keep calling for autopause on the CSV during the I/O peak. Does anyone have experienced this ? Here are the details : Environment Cluster: 2-node Failover Cluster Nodes: HV1 & HV2 (HPE ProLiant DL360 Gen11) OS: Windows Server 2025 Datacenter, Build 26100.32370 (KB5075899 installed Feb 21, 2026) Storage: HPE MSA 2070 full SSD, iSCSI point-to-point (4×25 Gbps per node, 4 MPIO paths) CSV: Single volume "Clsuter Disk 2" (~14 TB, NTFS, CSVFS_NTFS) Quorum: Disk Witness (Node and Disk Majority) Networking: 4×10 Gbps NIC Teaming for management/cluster/VMs traffic, dedicated iSCSI NICs Problem Description The cluster experiences CSV auto-pause events daily during a peak I/O period (~10:00-11:30), caused by database VMs generating ~600-800 MB/s (not that much). The auto-pause is triggered by HV2's CsvFs driver, even though HV2 hosts no VMs. All VMs run on HV1, which is the CSV coordinator/owner. Comparative Testing (Feb 23-26, 2026) Date HV2 Status Event 5120 SMB Slowdowns (1054) Auto-pause Cycles VM Impact Feb 23 Active 1 44 1 cycle (237ms recovery) None Feb 24 Active 0 8 0 None Feb 25 Drained (still in cluster) 4 ~60 (86,400,000ms max!) 3 cascade cycles Severe - all VMs affected Feb 26 Powered off 0 0 0 None Key finding: Draining HV2 does NOT prevent the issue. Only fully powering off HV2 eliminates all auto-pause events and SMB slowdowns during the I/O peak. Root Cause Analysis 1. CsvFs Driver on HV2 Maintains Persistent SMB Sessions to CSV SMB Client Connectivity log (Event 30833) on HV2 shows ~130 new SMB connections per hour to the CSV share, continuously, constant since boot: Share: \\xxxx::xxx:xxx:xxx:xxx\xxxxxxxx-...-xxxxxxx$ (HV1 cluster virtual adapter) All connections from PID 4 (System/kernel) — CsvFs driver 5,649 connections in 43.6 hours = ~130/hour Each connection has a different Session ID (not persistent) This behavior continues even when HV2 is drained 2. HV2 Opens Handles on ALL VM Files During the I/O peak on Feb 25, SMB Server Operational log (Event 1054) on HV1 showed HV2 blocking on files from every VM directory, including powered-off VMs and templates: .vmgs, .VMRS, .vmcx, .xml — VM configuration and state files .rct, .mrt — RCT/CBT tracking files Affected VMs: almost all Also affected: powered-off VMs And templates: winsrv2025-template 3. Catastrophic Block Durations On Feb 25 (HV2 drained but still in cluster): Operations blocked for 86,400,000 ms (exactly 24 hours) — handles accumulated since previous day These all expired simultaneously at 10:13:52, triggering cascade auto-pause Post-autopause: big VM freeze/lag for additional 2,324 seconds (39 minutes) On Feb 24 (HV2 active): Operations blocked for 1,150,968 ms (19 minutes) on one of the VM files Despite this extreme duration, no auto-pause was triggered that day 4. Auto-pause Trigger Mechanism HV2 Diagnostic log at auto-pause time: CsvFs Listener: CsvFsVolumeStateChangeFromIO->CsvFsVolumeStateDraining, status 0xc0000001 OnVolumeEventFromCsvFs: reported VolumeEventAutopause to node 1 Error status 0xc0000001 (STATUS_UNSUCCESSFUL) on I/O operation from HV2 CsvFsVolumeStateChangeFromIO = I/O failure triggered the auto-pause HV2 has no VMs running — this is purely CsvFs metadata/redirected access 5. SMB Connection Loss During Auto-pause SMB Client Connectivity on HV2 at auto-pause time: Event 30807: Share connection lost - "Le nom réseau a été supprimé" Event 30808: Share connection re-established What Has Been Done KB5075899 installed (Feb 21) — Maybe improved recovery from multi-cycle loop to single cycle a little, but did not prevent the auto-pause Disabled ms_server binding on iSCSI NICs (both nodes) Tuned MPIO: PathVerification Enabled, PDORemovePeriod 120, RetryCount 6, DiskTimeout 100 Drained HV2 — no effect Powered off HV2 — Completely eliminated the problem I'm currently running mad with this problem, i've deployed a lot of HyperV clusters and it's the first time i'm experiencing such a strange behavior, the only workaround i found is to take the second nodes off to be sure he is not putting locks on CSV files. The cluster is only running well with one node turned on. Why does the CsvFs driver on a non-coordinator node (HV2) maintain ~130 new SMB connections per hour to the CSV, even when it hosts no VMs and is drained?Why do these connections block for up to 24 hours during I/O peaks on the coordinator node? Why does draining the node not prevent CsvFs from accessing the CSV? Is this a known issue with the CsvFs driver in Windows Server 2025 Build 26100.32370? Are there any registry parameters to limit or disable CsvFs metadata scanning on non-coordinator nodes ? If someone sees somthing that i am missing i would be so grateful ! Have a great day.WAC can connect to itself or to other servers.
Hello, I have installed WAC with an internal certificate of my company. I can login to the web, the certificate appears correct in the browser. When I try to connect to the gateway itself or to other servers. No connection could be made because the target machine actively refused it: servergw.domain.com:6601 On event viewer: Event Winrest: Hosting failed to start Exception: System.InvalidOperationException: The requested certificate E=email address removed for privacy reasons could not be found in LocalMachine/My with AllowInvalid setting: False. The certificate is correct like other from company that used in other services, It has private key, and server authentication: E = email address removed for privacy reasons CN = email address removed for privacy reasons OU = company O = company bla bla L = City S = City C = Country I tried to create with other SAN: DNS=servergw.domain.com DNS=servergw DNS=localhost I have also tried to give permissions to the private key to Network Service, change the service to run with Local System. WinRM and trusted hosts are correctly. It only works when I install it with the self-signed certificate that WAC creates and it will say 60 days. What else can I try? Thanks !!
The file Microsoft_Server_InsiderPreview_LangPack_FOD_29531.iso is missing language packs.
Is it difficult to put these language packs in Microsoft_Server_InsiderPreview_LangPack_FOD_29531.iso? WinRe.wim PackageName PackageState ReleaseType InstallTime WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~~10.0.29531.1000 Installed FeaturePack 2/7/2026 15:07 WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~en-US~10.0.29531.1000 Installed LanguagePack 2/7/2026 15:07 WinPE-PlatformId-Package~31bf3856ad364e35~amd64~~10.0.29531.1000 Installed FeaturePack 2/7/2026 15:06 WinPE-PlatformId-Package~31bf3856ad364e35~amd64~en-US~10.0.29531.1000 Installed LanguagePack 2/7/2026 15:06 WinPE-PowerShell-Package~31bf3856ad364e35~amd64~~10.0.29531.1000 Installed FeaturePack 2/7/2026 15:07 WinPE-PowerShell-Package~31bf3856ad364e35~amd64~en-US~10.0.29531.1000 Installed LanguagePack 2/7/2026 15:07 WinPE-SecureBootCmdlets-Package~31bf3856ad364e35~amd64~~10.0.29531.1000 Installed FeaturePack 2/7/2026 15:07 WinPE-SecureBootCmdlets-Package~31bf3856ad364e35~amd64~en-US~10.0.29531.1000 Installed LanguagePack 2/7/2026 15:07 WinPE-UpdateOrchestrator-Package~31bf3856ad364e35~amd64~~10.0.29531.1000 Installed FeaturePack 2/7/2026 15:08 WinPE-UpdateOrchestrator-Package~31bf3856ad364e35~amd64~en-US~10.0.29531.1000 Installed LanguagePack 2/7/2026 15:09Can't download 29531
Hi can not download 29531 I get the below, I'm located in Sweden Error We are unable to complete your request at this time. Some users, entities and locations are banned from using this service. For this reason, leveraging anonymous or location hiding technologies when connecting to this service is not generally allowed. If you believe that you encountered this problem in error, please try again. If the problem persists you may contact Microsoft Support – page for assistance. Refer to message code 715-123130 and 2c3feb13-04f8-4432-bc28-c88fc015123b.
Did Microsoft make a mistake? WinServer 2022 Standard and up.
Microsoft removed functionality of Windows Deployment Service. I know their are ways to to get around this but they either are hackjobs or deploying your own windows with PE. as far as i know of writing this. I know I could go linux. they have a simple cd to follow. Or Mac has their own version for macs. but not microsoft. They THREW it away for some stupid reason. Do I really have to do a VM or worse ditch DNS & DHCP?
Encrypted vhdx moved to new host, boots without pin or recovery key
Hyper-V environment. Enabled VTPM on guest Server, 2022 OS and encrypted OS drive C:\ with BitLocker. Host server 2022 has physical TPM. Shut down guest OS and copied vhdx file to another Hyper-V host server that is completely off network (also server 2022 with a physical TPM). Created a new VM based on the "encrypted" vhdx. I was able to start the VM without needing a PIN or a recovery key. Doesn't this defeat the whole point of encrypting vhd's? Searching says that this should not be possible, but I replicated it twice on two different off network Hyper-V host servers. Another odd thing is that when the guest boots on the new host and you log in, the drive is NOT encrypted. So, where's the security in that? Does anyone have any ideas on this or if I'm missing something completely? Or have I just made Microsoft angry for pointing out this glaring flaw??Modernized Gateway Extension Support via WAC SDK
Hello, I would like to build a gateway plugin for the latest WAC v2511 but according to this documentation, the latest SDK package does not support the latest modernized gateway extensions. Is there a way to workaround this without downgrading WAC version? https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/extend/develop-gateway-plugin “The Windows Admin Center SDK and developer tools have not yet been updated to support development of gateway plug-ins compatible with the Windows Admin Center modernized gateway. Following this guide will not result in a .NET 8 extension compatible with the modernized gateway.BitLocker Network Unlock Question
I set up network unlock for two servers in our network as a test for a future deployment of BitLocker. Both HP's. One is a DL 360 Gen9 server with aftermarket TPM, the other is a DL360 Gen11 with onboard/HP TPM. Configured first NIC on both boxes for DHCP. Just to test things, I unplugged NIC1 but kept NIC2 plugged in on the Gen11 server and rebooted. It prompted for a PIN on boot up (expected behavior). Did the same test on the Gen9 server and it boots straight into the OS (unexpected behavior). As a further test, I kept NIC1 unplugged and then unplugged NIC2, rebooted and got prompted for a PIN (as expected since box was completely off network). Does anyone have any ideas why this is happening? Could it have something to do with the aftermarket TPM? From what I've read network unlock requires the first NIC to be DHCP so it can communicate with the WDS server and allow network unlock to work. Could it be something with the NIC's on the Gen9 server? I'm at a loss to explain this behavior. Hoping someone may have some insight. TIA
Shadow Copy with 6 days delay
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } Shadow Copy Windows Server 2022 Datacenter (VMWare 7.1) The MaxShadowCopies registry value has been increased to 256. Shadow Copies have been redirected to a different hard disk; FS=NTFS. The schedule is set to run three times per day. The maximum size is set to “Limit” with 1,700,000 MB. Current issue: Shadow Copies were available normally for several months. Now, suddenly, the Shadow Copies are displayed with a 6‑day delay.NTFS permissions are partially not working.
Participant A is sometimes unable to see Participant B’s files. The issue can be resolved by clicking the option: "Replace all child object permission entries with inheritable permission entries from this object." However, the problem keeps reappearing. Windows Server 2022 Datacenter (VMware 7.1), formatted as NTFS.
Recent Blogs
- 5 MIN READHello AskDS readers! Sagi and Adesh here. Today we’re excited to talk about a change that finally closes one of the longest‑standing troubleshooting gaps in Group Policy Preferences (GPP). G...Mar 04, 2026
- Hello again — this is Potti Tagore Nadh from Directory Services team. When troubleshooting Windows components, administrators often rely on enhanced logging to diagnose issues quickly and accuratel...Feb 27, 2026
