📎 AI Summary:
The forum thread discusses issues with public PCs configured to restore to a pre-set state after each reboot, using a Steady State-like setup. The original poster has tried gaining admin access via the Utilman and cmd hack but found that changes are wiped upon reboot, and cannot identify any active Steady State program or relevant Group Policy settings. The respondent suggests taking a disk snapshot to investigate the boot configuration and recommends reformatting and reinstalling Windows as a potential solution if multiple recovery partitions are present.

nater1r

New Member
Joined
Nov 25, 2015
Messages
2
Thread Author #1
Old management company left us with public PCs with Steady State type of setup. After a reboot PCs restore back to preconfigured state, which isn't necessarily a bad thing. However, Old IT did not leave admin passwords or ability to customize new settings. New IT guy is overwhelmed with other projects. I have some IT experience and have thus been tapped to try to come up with a solution. I was able to use the old Utilman and cmd hack to access to admin account, but any changes were wiped after reboot. Was not able to find any Steady State type program running and there was nothing obvious in the Group Policy settings.
 

Solution
Take a snapshot of the Windows disk manager... I'd assume a efi or network recovery partition is behind the mystery boot wipe. If so then (after backups) a format and reinstall of new Windows would be my next step.

ussnorway

Windows Forum Team
Staff member
Joined
May 22, 2012
Messages
4,597
Take a snapshot of the Windows disk manager... I'd assume a efi or network recovery partition is behind the mystery boot wipe. If so then (after backups) a format and reinstall of new Windows would be my next step.
 

Solution