I have been searching the forums for a while but none of the suggestions I have seen work for this problem.I am running Windows XP with SP3.I am running Steady State 2.5Any time I log in as the user that Steady State is restricting then logoff, login again as admin, and attempt to edit the user settings for the restricted profile it gives me error "This user cannot be edited because the profile is currently in use. Ensure that this user is properly logged off, and try again."I have deleted and recreated ALL accounts.I have tried reinstalling Steady State.I have installed UPHClean.My virus scan and firewall ARE NOT blocking Steady State.None of the above have worked.Please Help!!!!

Hi Matt, have you disabled antivirus program and checked the result? If so, let's check if UPHClean service is started: 1. Click Start, go to run, type services.msc and press Enter. 2. Locate User Profile Hive Cleanup on the right panel. 3. Double click it and make sure it is started and the Startup type is Automatic. 4. Then, please restart the computer and check the result. Meanwhile, please let me know if the error also occurs after creating a new account in Windows XP or Windows SteadyState.

This only happens when I work on an account created in SteadyState. An account made on Windows is ok unless I turn on any restrictions. UPHClean is turned on and it's Startup is set for automatic and I still can't edit the account.

Hi Matt, can we use the following workaround for current issue? 1. Remove the account from Windows SteadyState. 2. Create the account again in Windows. 3. Since Windows SteadyState can detect the account, you can still set restrictions on it.

Is there any solution to this problem. I have created accounts both ways and I still get that error message.

Hi,Can you use handle.exe to find out if any handles are open to objects under the user's profile? You can get handle.exe here. So, log on as the restricted user, then log off. Log on as the administrator, open cmd.exe, and run handle.exe: C:\> handle RestrictedUserHandle v3.41Copyright (C) 1997-2008 Mark RussinovichSysinternals - www.sysinternals.comSystem pid: 4 7E4: C:\Users\RestrictedUser\NTUSER.DAT{0f69446d-6a70-11db-8eb3-985e31beb686}.TM.blfSystem pid: 4 824: C:\Users\RestrictedUser\ntuser.dat.LOG1System pid: 4 8B4: C:\Users\RestrictedUser\ntuser.datReplace "RestrictedUser" with the name of your restricted user account. With a little luck, this will help track down why the profile is locked.Thanks,Rob ElmerDevelopment LeadWindows SteadyState

I just now ran the handle and this what I got: System pid: 4 94C: C:\Documents and settings\students\NTUSER.DAT System pid: 4 9D0: C:\Documetns and settings\students\ntuser.dat.log What does this mean. Thanks in advance.

Somebody please help me.

How can this help track down why the profile is locked? Handle v3.41Copyright (C) 1997-2008 Mark RussinovichSysinternals - www.sysinternals.com System pid: 4 918: C:\Documents and Settings\Laptopuser\ntuser.dat.LOGSystem pid: 4 964: C:\Documents and Settings\Laptopuser\NTUSER.DATSystem pid: 4 C10: C:\Documents and Settings\Laptopuser\Local Settings\Application Data\Microsoft\Windows\UsrClass.datSystem pid: 4 C3C: C:\Documents and Settings\Laptopuser\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG

If you use [auto login] then it happens. change: 1.login(use administrator account) 2.type "control userpasswords2" at command line, check [all users need to input passwords] 3.reboot 4.login(use administrator account) 5.run steadystate ,change user setting

@ hungyuhsun ... err no... "If you use [auto login] then it happens." is absolutely not expected behaviour I have 70+ systems running SteadyState v2.0 & v2.5, all using autologin, either with or withouta password. These clean built systemswork without fail - I can logout of a restricted user, login via Administrator, and alter the SS settings for that user. I can logout, login, and edit theSS profileas many times as I wish without a problem. I have the Windows firewall, eTrust AV, and UHPClean 1.6d service installed..... However, on all 10 systems which I upgraded from v2.0 to v2.5 I have had no end of issues (all caused because there is no migration capability for SS accounts with restrictions - do not attempt an upgrade with any restrictions on any accounts). Even though I have overcome all of these, all 10 of these upgraded systems now refuse to allow me to edit the SS profile -"Profile is currently in use". I have to create/alter the password for the user to prevent autologin at next reboot to be able to access the SS profile. I have tried a huge amount of things, inc: 1) Remove SS and all files, folders and reg settings 2) Remove UHPClean 3) Creating/testing withnew accounts 4) Copying profile to new account etc etc So far, no luck.I always get the"Profile is currently in use" error when I put it all back together. I am convinced that if either an SS install has been tried, then reversed out, or upgraded, or uninstalled/reinstalled at some point, then some (registry) setting get screwed up, and is not reset correctly, causing this issue. Remember, when ever you edit or remove SS it changes a considerable amount of settings with have nothing to do with the single edit/restriction you may be working on. (e.g. a simple and obvious example is when you uninstall SS it re-instates the Security Center Service !?!?!?) I have not yet had time to test the newUPHClean v2.0 beta release 31st Oct 2008 http://blogs.technet.com/uphclean/which may solve this issue. ps Apologies if there are multiple postings of this... the Technet Alert Me service crashed out, and didn't appear to add this reply to the thread. However,after two more attempts, all 3 copies of this reply appeared. Now it seems impossible to delete the last two....

Hmm... I am getting this problem too... cant seem to solve it

SteadyState is such a panacea for those of us working/administering Public PCsin libraries , but it sure would be nice if thiserror/glitch"Profile is currently in use" could be fixed - or a workaround provided. I have found that it almost always happen the first time I login/logoff a patron/user account and then log back in as admin to re-apply SteadyState restrictions. Using the handle.exe suggestion previoulsy mentioned byElmer, sure enough the culprit is user.dat and user.dat.log, but what can you do with that tidbit of information? Can they be killed ( and if so how) and then one can re-open SteadySate to click on a user account without getting the"Profile is currently in use" error. Trying the new beta UPHcleaner didn't help things at all.I have found that the only thing that works is to reboot the machine...Anything new on this front?Funny how this wasn't an issue with the old Microsoft Shared Computer Toolkitanr

I agree with meangreene,The only thing that worked, is shutdown and re apply new restrictions. I tried everything listed above but none seems to work as intended. I'm using win vista OSMhnd.

I think, I found a solution. Shut down the computer. Start it and hold Shift while loading. On the log on screen - go under administrator and the profile will work. I think stopping Windows from loading any of the profiles in the beginning helps. Good luck. Works with Vista also.

To get around this issue, I just restarted, logged out of the restricted user account (it is set to auto-logon), logged in as admin, and was able to edit the SteadyState profile. This shows that it isn't always necessary to halt the auto-logon to avoid this issue. (SyncBack v2.5 on XP SP3)

I had this same issue and also could not disable autologin no matter what I did so I could not "Unlock" this profile (even after reboot) I read a thread somewhere about if .NET was installed, it would force a login. I checked the add/remove area and sure enough .NET 1.1 was not installed on the PC. Once installed it, with SP1 and the update afterwards and rebooted, it came up to the login screen (it did not force auto-login). I logged in with Administrator and was able to modify the profile.

I had this same issue and also could not disable autologin no matter what I did so I could not "Unlock" this profile (even after reboot) I read a thread somewhere about if .NET was installed, it would force a login. I checked the add/remove area and sure enough .NET 1.1 was not installed on the PC. Once installed it, with SP1 and the update afterwards and rebooted, it came up to the login screen (it did not force auto-login). I logged in with Administrator and was able to modify the profile.