In production environments, if users see a warning stating that someone else is using their PC whenever they request a restart or shutdown after a Windows update, administrators should not immediately assume that the message itself is the cause. Instead, they need to check separately whether this is an update issue and examine the state of user sessions. This case occurred on a laptop running Windows 11 24H2 Enterprise that had received this month’s cumulative update, even though no other user was actually connected.
The warning reads, “Someone else is still using this PC,” followed by an explanation that restarting could damage another user’s unsaved work. Because this can instead cause anxiety and interrupt business operations, administrators must document whether the update was installed and under what conditions the warning appeared before deciding whether to temporarily roll back the update.
The original thread reported that uninstalling KB5127648 made the message disappear, while reinstalling it caused the warning to return. Although this correlation alone cannot pinpoint the exact defect inside Windows, it provides sufficient grounds to examine the update installation state before considering user error or a security breach.
Separate the Update Issue From the Warning Message
The key to this issue is determining whether the message displayed on the screen matches the actual session state. The organization confirmed that no other users were connected, the problem was reproduced on an affected PC, and the warning disappeared and returned following the removal and reinstallation of the update. Administrators therefore should not automatically interpret the warning as a safety signal and terminate user sessions. Instead, they should compare the update states of affected and unaffected PCs under the same conditions.
First, check the Windows 11 Enterprise build and whether KB5127648 is installed on both the affected and unaffected PCs. You can view the list of installed updates by running the following command in an elevated PowerShell window.
Get-HotFix | Sort-Object InstalledOn -Descending
The command results will not identify the cause of the warning on their own. Compare PCs on which KB5127648 appears with those where it does not, and save the results from before and after the update separately so they can be compared with subsequent reproduction attempts. Install, remove, and reinstall the update on test equipment or during an approved maintenance window, taking the organization’s change-management procedures and service-stability requirements into account.
Step-by-Step Verification Procedure
First, with KB5127648 installed, perform a restart and a shutdown separately, recording the warning message, its occurrence time, and whether each operation completes normally. Second, remove the update and repeat the same procedure on the same PC. Third, if possible, reinstall the update and determine whether the warning reappears. These comparison records provide a clearer basis for assessing causality than screenshots supplied by users.
The scope of the verification should also be expanded. If the same results appear across multiple users and PCs, the organization gains stronger grounds to reflect the issue in its update-management practices. If the warning is limited to a single PC, separately investigate factors outside the update, such as drivers, security software, user profiles, and local administration tools. Because the original report does not identify the exact location of the underlying defect, administrators should not blame a specific component at this stage.
When Administrators Should Roll Back the Update
At present, the key signal is the observation that removing KB5127648 makes the warning disappear, while reinstalling it causes the message to return. If the warning appears but restarts and shutdowns complete normally with no data loss, administrators may consider temporarily rolling back the update until official resolution information becomes available. Conversely, if the organization confirms the loss of unsaved work or actual operational disruption, it should reassess its update-retention strategy at the organizational level.
Although the original report advises administrators to tell users to ignore the warning, doing so does not mean the update defect has been resolved. It is a temporary operational decision intended to reduce inconvenience. Administrators should separately verify that systems shut down normally after the warning is ignored, check for other errors, and confirm that saved files are unaffected. Rather than leaving the update issue to users, the safer approach is to collect status information from the administrator console and communicate the affected equipment and conditions.
Responses to Avoid
Administrators should not assume that another user is logged in merely because the warning appears, nor should they forcibly clear user sessions. This case confirmed that no other user was connected, and the warning itself—not the actual session information—was the problem. They should also avoid concluding that Windows files, drivers, or security software were damaged and beginning remediation solely because the warning disappeared after the update was removed.
It is equally important not to speculate about or share nonpublic user information and session contents without evidence of a security incident. Administrators should document confirmed facts, reproduction conditions, differences from unaffected PCs, and temporary mitigation measures separately. After confirming whether an official fix is available, they can determine the organization’s next update policy. This approach turns the response into a structured verification process that reduces unnecessary confusion for both users and the organization.
What to Do Now
- Collect the PowerShell
Get-HotFixresults from affected and unaffected PCs, then compare whether KB5127648 is installed. - Perform a restart and a shutdown separately with KB5127648 installed, recording whether the warning appears and whether each operation completes normally.
- On approved test equipment, repeat the same procedure after removing the update and document the before-and-after differences in the change record.
- Reinstall the update on equipment where the issue can be reproduced, confirm whether the warning returns, and determine whether it is limited to one PC or affects multiple systems.
- Check for lost work and additional errors, then use the change-management process to decide whether to temporarily roll back the update until an official fix is available.
Source
This article was prepared by reviewing the following original source: r/sysadmin — KB5127648 causing “Someone else is still using this PC” message

Leave a Reply