I am on my 4th reinstall of the OS due to 24H2 within the past two weeks.
But I have put a block on that in the meantime whilst I await a resolution from Razer using a Registry tweak.
But I have been repeatedly getting these issues over the past 2 week period too.
My hardware is a 2024 Razer 18 with 4090 GPU / 300Hz QHD Display and G-Sync.
I had setup a custom 3D settings profile -and had said Power Management Mode - Max Performance. I have since reset this to normal - thinking that would stabilise things.
However not long after (6 seconds) I got a series of Events - Source RestartManager, EventID 10010, for 4 processes, saying things like this (only the pid varies):
Application ‘C:\Program Files (x86)\Battle.net\Battle.net.exe’ (pid 14036) cannot be restarted - Application SID does not match Conductor SID…
When I interrogate the Battle.net Properties, I now see a weird entry,
Account Unknown (S-5-21-3259…) in the Groups or user names.
The timestamps for these:
27-08-2025 19:24:27 for the Power Event
19:24:33 to 19:24:39 for the series of RestartManager Events.
When I talked with Co-Pilot about this, it came up with a script to fix the ACLs:
@echo off
setlocal enabledelayedexpansion
:: Timestamped log setup
set LOG=%USERPROFILE%\Desktop\ACL_Teardown_%DATE:/=-%_%TIME::=-%.log
echo === ACL & SID Teardown Started: %DATE% %TIME% === > "%LOG%"
:: Target paths
set TARGETS="C:\Program Files (x86)\Battle.net" "C:\Program Files (x86)\Diablo III" "C:\Users\Public\Desktop\Battle.net.lnk"
:: Step 1: Audit ACLs
echo [*] Auditing ACLs... >> "%LOG%"
for %%T in (%TARGETS%) do (
echo --- ACLs for %%~T --- >> "%LOG%"
icacls %%~T /T >> "%LOG%"
)
:: Step 2: Dump SID mappings
echo [*] Dumping SID mappings... >> "%LOG%"
wmic useraccount get name,sid >> "%LOG%"
:: Step 3: Take ownership and reset ACLs
echo [*] Resetting permissions... >> "%LOG%"
for %%T in (%TARGETS%) do (
echo --- Resetting %%~T --- >> "%LOG%"
takeown /F %%~T /R /D Y >> "%LOG%"
icacls %%~T /reset /T >> "%LOG%"
)
:: Step 4: Confirm orphaned SID removal
echo [*] Re-auditing ACLs post-reset... >> "%LOG%"
for %%T in (%TARGETS%) do (
echo --- Post-reset ACLs for %%~T --- >> "%LOG%"
icacls %%~T /T >> "%LOG%"
)
echo === ACL & SID Teardown Completed: %DATE% %TIME% === >> "%LOG%"
echo Done. Log saved to: %LOG%
pause
In summing up, it said this:
What the Script Does Fix
• Removes entries from ACLs
• Resets permissions to default for key folders and shortcuts
• Logs SID mappings and ACL states for postmortem analysis
• Reclaims ownership from synthetic or containerized identities
What It Doesn’t Fix (Yet)
• Registry residue: Battle.net and Diablo III write container mappings and telemetry flags to the registry. These can reintroduce instability unless purged.
• AppData/ProgramData remnants: Uninstalls often leave behind config files, logs, and container tokens that can reassert broken identities.
• Overlay injection: Razer, THX, Realtek APOs, or even Battle.net overlays may still inject DLLs at runtime, causing access violations or container drift.
• Telemetry or auto-update triggers: Battle.net may silently reapply container logic unless blocked or sandboxed.
• Driver-level fallout: If the GPU power event corrupted memory mappings or driver state, ACL resets won’t fix runtime injection failures.
–
Does Blizzard have a fix script that caters to all these points? I can’t believe I am the only one experiencing these issues.
I issued a ticket with Issue ID: #100690509 back on Aug 16th when my stability issues with Diablo 3 commenced.
The Container/SID reared it’s ugly head on the 4th install yet again. Only a day or two game play and I am back where I was before. NVidia Experience on a prior install I think caused issue too - that installed then updated then crashed mid video capture and totally borked machine then too.
I then asked Co-pilot: Would a restore point undo all this?
The answer:
A restore point might undo some of it—but not all, and not reliably. Here’s the breakdown:
What a Restore Point Can Undo
• Registry changes: If the orphaned SID or container mappings were introduced via registry edits, a restore point created before the power event could roll those back.
• System files and permissions: It may revert ACLs on system-critical files if they were altered.
• Driver states: If the GPU or Razer stack injected unstable modules, a restore point might revert those to a previous version.
What It Won’t Touch
• User-created files and folders: ACLs on things like your Diablo III install or Battle.net shortcut won’t be reverted unless they’re part of system protection.
• AppData, ProgramData, and container remnants: These folders are outside the scope of System Restore.
• Orphaned SIDs in ACLs: Restore points don’t clean up ACL drift or synthetic identities unless the entire object is rolled back.
• Telemetry or auto-update triggers: If Battle.net reasserted container logic post-restore, the issue could reappear instantly.