Tranquil IT Forum

- WAPT Version: 2.6.0.17226 Enterprise
- Server OS: Linux Debian
- Administration Machine OS: Windows 11

Hello,

I recently created a thread about a problem migrating from Windows 10 to Windows 11, thinking it was due to outdated graphics drivers.

However, I found the source of the problem: unknown profiles. An Active Directory migration was performed on my network, and as a result, some profiles became unknown. (The issue is that there are duplicate accounts linked to the unknown profiles, so if I delete the unknown profile, it will delete the linked profile, and vice versa.)

I had a test PC with unknown profiles, so I deleted them, which also deleted the profiles linked to them.


If anyone could guide me on how to resolve this problem, I would be very grateful.

Thank you in advance!

Hi Stan,

I'm quite surprised by this behavior because we've never encountered this issue, even though we have many clients who also perform domain merges (our second area of ​​expertise with WAPT is Samba Active Directory).

For your test, how did you delete the profile? Did you delete both the directory in c:\users and the registry key SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList?

In your case, is it the c:\users\myuser profile that is pointed to by both the old and new SIDs in the registry (key above)?

With an auditing package, you can search for problematic profiles and even delete the problematic registry keys by matching them to the SID of the old domain.

Best regards,

Denis

dcardon wrote: ↑June 2, 2025 - 3:37 PM Hello Stan,

I'm quite surprised by this behavior because we've never encountered this issue, even though we have quite a few clients who also perform domain merges (our second area of ​​expertise with WAPT is Samba Active Directory).

For your test, how did you delete the profile? Did you delete both the directory in c:\users and the registry key SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList?

In your case, is it the c:\users\myuser profile that is pointed to by both the old and new SIDs in the registry (key above)?

With an auditing package, you can search for problematic profiles, and even delete the problematic registry keys by matching them to the SID of the old domain.

Best regards,

Denis

Hello Denis,

So, to fix the problem, I added a PowerShell script to the Windows 11 installation:





This script removes all invalid profiles from the registry key SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. It compares these profiles with the Active Directory list using the command: `$validUsers = Get-CimInstance Win32_UserAccount | Where-Object { -not $_.LocalAccount } | Select-Object SID`

Sincerely,

Stan