Remote Desktop Session Host (RDSH) user profile disks (UPD) have the same uniqueid disk number on Widonws 2025 farm

2026-09-15T08:07:49.6866667+00:00

On my RDS servers, every new user profile upd vhdx contains the same UniqueID as the master UVHD-Template.vhdx file.

Event:158, source:Disk
The identifiers for disk 3 are identical to those of at least one other disk on the system. Visit the Microsoft support website (http://support.microsoft.com) and refer to KB2983588 to resolve the issue.

To work around, I have to perform a ResetDiskIdentifier on each new vhdx upd disk.

Luc

Windows for business | Windows Server | User experience | Remote desktop services and terminal services
0 comments No comments

1 answer

Sort by: Most helpful
  1. VPHAN 43,565 Reputation points Independent Advisor
    2026-09-15T08:45:01.2133333+00:00

    Hi ServiceInformatiqueICONsa-8160,

    your RDS farm is generating Event ID 158 because the connection broker provisions new user profiles by executing a raw file copy of the master UVHD-Template.vhdx. This primitive cloning mechanism perfectly duplicates the internal disk signature. When multiple users log into the same Session Host, the operating system mounts multiple virtual hard disks containing the exact same disk identifier, which immediately triggers the collision warning in the Event Viewer.

    Microsoft has not updated the UPD provisioning engine to randomize signatures upon creation, there is no registry toggle to alter the broker's behavior. To avoid running the reset command manually, you must automate your workaround. You can open the Task Scheduler on your RDSH nodes and create a task triggered by user logon events, specifically looking for Event ID 1149 in the TerminalServices-RemoteConnectionManager operational log. You can attach a PowerShell script to this task that executes the ResetDiskIdentifier command against the newly mounted volume, automatically clearing the collision the moment the profile is generated.

    However, the most architecturally sound resolution for a modern Windows Server 2025 deployment is to deprecate User Profile Disks entirely and migrate your users to Microsoft FSLogix Profile Containers. FSLogix is the official enterprise successor to UPDs and is licensed at no additional cost for environments holding RDS Client Access Licenses. The FSLogix agent dynamically compiles, formats, and mounts the VHDX containers during the initial user login rather than executing a raw template copy. This advanced provisioning mathematically guarantees that every single profile disk possesses a completely unique identifier, permanently eliminating the Event ID 158 collisions while providing vastly superior login performance.

    Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

    VPHAN

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.