none
Error: "Windows cannot copy file. The filename or extension is too long."

    Question

  • I just downloaded and installed SteadyState. I locked three users, but when the user logged on, they all got an error message, "Windows cannot copy file (file name..) Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator. DETAIL - The filename or extension is too long. 

     

    I can't find the file that is listed in the error message.

    I unlocked the profiles and took off all the restrictions except blocking firefox and netscape. I am still getting the error message. How can I fix this?

    Sunday, March 09, 2008 3:49 PM

Answers

  • Hi,

     

    We occasionally see this with locked profiles.  When a profile is locked, Windows copies the original profile directory (often c:\users\user.orig) to a temporary location (often c:\users\user).  During the user's session, changes the user makes are written to this temporary location.  When the user logs off, Windows deletes the temporary profile, thus cleaning up his changes.

     

    When you see the warning about filenames being too long when the locked user logs in, the problem is usually that temporary internet files created by Internet Explorer exceed the default 260 character path length limit, so Windows encounters an error when it tries to copy these files to the temporary location.  It's possible that other applications could create long filenames/paths that cause similar problems.

     

    I've been able to solve the problem by unlocking the profile, logging in as the restricted user, then emptying the user's temporary internet files in Internet Explorer.  Then log off, log on as the Administrator again, and re-lock the user's profile.

     

    Hope that helps.

     

    -Rob

     

    Friday, June 13, 2008 4:10 AM
  •  

    Hi BeGr,

     

    Thanks for posting here!

     

    From the post, I understand that locked users cannot log on the computer with error "Windows cannot copy file", "The filename or extension is too long".

     

    After checking the error, this issue can be caused by one or more internet temporary files with long filename. In order to check the cause of the issue, please let me know the file and its location. If we make sure the issue is caused by internet temporary files, we can remove the folder and check if the issue is resolved.

     

    Best regards,

    Monday, March 10, 2008 3:47 AM
    Moderator

All replies

  •  

    Hi BeGr,

     

    Thanks for posting here!

     

    From the post, I understand that locked users cannot log on the computer with error "Windows cannot copy file", "The filename or extension is too long".

     

    After checking the error, this issue can be caused by one or more internet temporary files with long filename. In order to check the cause of the issue, please let me know the file and its location. If we make sure the issue is caused by internet temporary files, we can remove the folder and check if the issue is resolved.

     

    Best regards,

    Monday, March 10, 2008 3:47 AM
    Moderator
  • As my message said, I can't find the file that is listed in the error message. I went into file Explorer and expanded the folders. The folder listed in the error message does not exist. So how can I delete something that isn't there?

     

    I have since uninstalled SteadyState and tried to restore from a Security Restore point. The restore from a Security Restore point failed, so I went back to a previous one. That failed too. I can't get things back the way they were.

    Even after I uninstalled, it was taking forever to create the Temp folder when I logged in, so now I have created new user accounts that replace the old ones. They are not controlled by SteadyState. Can I get the create the Temp folder thing to go faster?

    How can I straighten out the mess that SteadyState created? Before I delete the old user accounts, how can I save all the settings from them? Or how can I restore the system to what it once was? The old accounts are limited ones, so is that keeping SteadyState installed on those accounts?

    My reason for trying SteadyState is that I want my kids to use Internet Explorer, not Firefox or Netscape, because my parental control software does not work on them. How can I lock IE as being the only browser allowed? How can I keep my kids from using proxy sites to go to Facebook and MySpace to get around the parental controls? There are thousands of them, with new ones created every day. It is useless to block specific URLs.

    Wednesday, March 12, 2008 2:19 PM
  • To the original issue. I would like to confirm the file location first. IE temporary folder?

     

    If so, we can delete IE temp files with the following steps:

    ===========

    1. Click Start and click Run.

    2. Type “inetcpl.cpl” in the open box, and then press Enter.

    3. Click "Delete Cookies" and select OK when prompted to confirm.

    4. Click "Delete Files" and select OK to confirm.

    5. Click "Settings", and then click "View Files". Delete all files in this folder.

    6. In the Settings window, click "View Objects". Delete all the objects in this folder. If some objects cannot be deleted, please restart the computer and try again.

     

    Uninstall SteadyState will restore the system to the original status. However, before uninstalling, please make sure all the restrictions have been disable, users have been unlocked. WDP has been disabled.

     

    Best Regards,

    • Proposed as answer by Cesabarre Sunday, October 03, 2010 11:37 AM
    Thursday, March 13, 2008 1:57 PM
  • Sean wrote:

     Sean Zhu - MSFT wrote:

    From the post, I understand that locked users cannot log on the computer with error "Windows cannot copy file", "The filename or extension is too long".

     

    After checking the error, this issue can be caused by one or more internet temporary files with long filename. In order to check the cause of the issue, please let me know the file and its location.

    Sean,

     

    I have the same problem. You misread the original post: the error is not "too long filename", it is "no permission" -- AND, we're dealing with files that do not even exist!

     

    I just set up SteadyState on my senior-citizen dad's computer. Same thing: he can't login, because it complains that various (random!) filenames can't be copied. The filename is different every time. And they are names I've never heard of, with dates in the name, etc.

     

    If that is not enough to help you, I will attempt to write down some of the names next time I have access to his computer.

     

    Thursday, June 12, 2008 2:36 PM
  • I had a similar experience on one PC after making some adjustments on three machines all running XP Pro SP2 with Steady State already installed.

    Eventually, the only way I could get round the problem was log back in as administrator, go to Control Panel, Users. Delete the user including files. Then set up the user name again.  Login as the new user, let windows configure the user and finally log back into administrator and set up the user’s restrictions within Steady State.

    Not the best cure but it worked for me.

     

    Thursday, June 12, 2008 4:18 PM
  • Hi,

     

    We occasionally see this with locked profiles.  When a profile is locked, Windows copies the original profile directory (often c:\users\user.orig) to a temporary location (often c:\users\user).  During the user's session, changes the user makes are written to this temporary location.  When the user logs off, Windows deletes the temporary profile, thus cleaning up his changes.

     

    When you see the warning about filenames being too long when the locked user logs in, the problem is usually that temporary internet files created by Internet Explorer exceed the default 260 character path length limit, so Windows encounters an error when it tries to copy these files to the temporary location.  It's possible that other applications could create long filenames/paths that cause similar problems.

     

    I've been able to solve the problem by unlocking the profile, logging in as the restricted user, then emptying the user's temporary internet files in Internet Explorer.  Then log off, log on as the Administrator again, and re-lock the user's profile.

     

    Hope that helps.

     

    -Rob

     

    Friday, June 13, 2008 4:10 AM
  • OK, I've solved the problem here.

     

    Now that I understand how locked profiles work, the solution is pretty clear:

     

    In a locked profile,

    * SteadyState renames the original user name "Joe" to "Joe.orig"

    * When "Joe" logs in, the entire Joe.orig folder is copied to a new Joe folder

     

    -->Wonder why login takes so long? See how big the Joe.orig folder is!

    -->Wonder why a file can't be copied? Check out its attributes in Joe.orig!

     

    In my case, I had a few misc "surprise" files in the root of Joe.orig that needed deleting. And after removing 400MB of extra stuff from the profile, the user is able to start up reasonably quickly.

     

    Saturday, June 14, 2008 2:32 PM
  •  

    This sounds very much like the issue I have been having. Can a script be written to run at shutdown that will clear out the temp folder so that the issue will not repeat?
    Tuesday, July 15, 2008 6:11 PM
  • I´ve the same problem with a locked useraccount.
    Today I wrote an easy skript, ok, maybe more an one-liner...
    The curius thing is, if I execute the command (rd /S /Q "C:\***FULLPATH***\Temporary Internet\") over cmd.exe it works fine, but if I put this code in a .bat or .cmd file, it just don´t work.

    Do anybody has an idea why it don´t work?

     

    BTW sorry for my poor english Wink



    EDIT: The reason was the charset of the script. The path contained the letter "ü". I´ve solved the problem by using DOS-shortnames.

    I added the script by using gpedit.msc and it seems to working nice.

    Sunday, August 10, 2008 8:04 PM
  • We had similar problems. If a machine is improperly shut down(power outage etc), the temporary users account could remain active causing this login error. We resolved this issue with a bat file that simply removes the temporary users folder at start up. ie

     

    cd c:\documents and settings
    RmDir user /s /q                             
    exit

     

    This batch file is run from gpedit.msc \computer configuration\windows settings\scripts\startup

     

    Tuesday, August 12, 2008 3:37 PM
  • you dont know anything do you

    Sunday, August 17, 2008 2:10 AM
  •  

    I would like to run that batch file  

     

    "cd c:\documents and settings
    RmDir user /s /q                             
    exit"

     

    from gpedit.msc\user configuration\windows settings\scripts\logoff.  However, when I do, the computer "hangs" at the "Running logoff scripts"  dialog box during the logoff process.  Is there anyway around this?  any code I can add to the batch file???

     

    Thank you....

    Thursday, September 04, 2008 6:38 PM
  • I have no problems running it in either logoff or startup. I assume you didn't include the " and that you changed the word user for your users actual name.

     

    I chose to run it at startup because we have some users that will not properly shut the system down. They were just turning the power strip off and that allowed them to bypass any shut down scripts.

    Thursday, September 04, 2008 11:00 PM
  • This is the location of the problematic file:

    Local Settings\Temporary Internet Files\Content.IE5\5P

    We are having the same issue and it is very annoying to have to go to the different branches to clean out the file.  I am looking for a script or something that can run to clean this out since Steady State is unstable when it comes to this.

    Monday, December 29, 2008 5:09 PM
  •  

    THE SOLUTION PLEASE !!!!!!!!!!!!!!!!!!!

     

     

    The solution it's very easy, for not have this problem of copy name file very long :  SELECT in SECURITY SETTINGS in WINDOWS STEADY "Dot no allow Windows to compute and sotre passwords using LAN Manager Hash values".

     

    With this is selection the problem is STOP, but don't forget delete folder of your limited session in C\Documents and Settings ; you see for example two folders :

     

    cyber and cyber.orig, delete cyber and with the selection i have say you, the problem it's finish.

     

    Thanks, and good luck !

    Friday, January 09, 2009 7:01 PM
  • I'm having the same intermittent problem with filename too long. As for Benbenben7's solution, we do have "Do not allow Windows to compute and sort passwords using LAN manager hash values" selected in Steady State, and are still getting the error. A fix for this problem would be much appreciated.
    Thursday, March 05, 2009 10:06 PM
  • This is crazy! Has anyone come across a permanent solution for this? It seems to be somewhat of a common occurrence. I can delete the profile which corrects the issue, but wow what a horrid thing to consistently manage. The whole point of Steady State is to cut down on the management of public access computers.
    Monday, March 09, 2009 8:56 AM
  • Hi everyone
    I am looking for a solution for this issue also.  I take care of some labs at a small community college and this is a recurring issue in one and one only lab.
    I assure you all that this has nothing to do with Steady State.  I actually have been looking at SS as a possible solution for this, and just downloaded it to a test computer which is not connected to this lab.
    This issue of long filenames/no login has been happening in this lab for several months.  I inherited this lab and have no documenation so have had to figure out a lot of it.    When I started last fall I first noticed that the antivirus was a version that expired 5 years ago, and from a company that we no longer even use.  So all the comps were infected and that is an aspect that I have been looking into.  I believe I did fix them all though.
    This lab has one student login, and it is a Mandatory profile located on an Active Directory server.   This lab is its own domain. 
    Late last fall this longfilename issue started to appear.   Like some of you, I found that the files will not delete, and the only way to restore login is to login as administrator, delete the entire student profile, and relogin as student.  This always works.   However, it obviously is time consuming, to say the least.
    I have made entirely new profiles twice now, thinking that somehow there is an infection or some other glitch that my many repeated scans has not found.  
    I just completed one new profile on Sunday.  it worked very well for all the classes until today, and I am now at one computer that would not login, with that longfilename error message.
    The message says  ( I have saved it and some screen shots which I can send if anyone wants to see) that windows cannot copy "xxxxx...." (longfilename) from the server to the C: drive, and that the filename is too long. 
    This message had always confused me, as there was never anything in that location on the server.   I  found some time ago that the file is always actually located on the local machine....  \local settings\temp\TIF\(subfolder) and then the name.     Today, there are several files in that location with longfilenames.   I am sure that the one named was only the first of several and any of them would have prevented login.  
    A right click on some of these gives a menu that inclues 'print' so I did. The files I printed were 'png' files. After a long time, the wizard did deliver prints, I did two different ones, and they were images, one of a restaurant ad, one from Best Western hotels.
    The right click menu also has 'scan with antivirus' but that does not work.   ???
       At other times these have not been the offending names, but something else which I don't recall just now; I can look that up again.     But before, there was nothing I could do with the LFN files; not open, scan, preview, nothing.  And, they don't always give the same rightclick menu either. 
    This is all I have at the moment.   It's late and I am tired.  But I am excited to find that others are having this same issue, as I have been looking all over the place for 3 months.   Hopefully we will find a real solution.   That script seems to offer possibilities. 
    Friday, March 13, 2009 3:43 AM
  • Hi,

    Generally the problem is that files with absurdly long names are generated in a user's Temporary Internet Files directory.  When a mandatory roaming profile is in use, Windows copies the original profile tree (c:\users\restricteduser.orig) to a temporary location used for the logon session.  If Windows encounters path names longer than 259 characters during this copy, the operation fails and the user cannot log in.

    Therefore, the trick is to prevent long paths like that from appearing in the .orig profile.  You can open SteadyState, unlock the profile, then log on as that user and empty the user's temporary internet files by using start > control panel > internet options, then clicking "delete..." under the Browsing History section of the General tab.  Then log off, log on as administrator, and relock the profile using SteadyState.  Once the profile is locked, it should stay clean because any new temporary files are written to the temporary profile location used for that logon session.  If the profile is unlocked for maintenance, however, keep in mind that you'll have to remove the temporary internet files again before logging off that user before you relock the profile.

    Thanks,
    Rob Elmer
    Development Lead
    Windows SteadyState
    Sunday, March 15, 2009 6:45 PM
  •  Well Rob, that's a good explanation but not really any help, as having to do that requires an admin to go to the comp, which is what Steady State and mandatory profiles are supposed to help avoid.

    Also, your comment at first talks about "roaming mandatory profiles"; by this I think you mean a profile that has been created/configured initially as roaming, and then reconfigured to mandatory.   Good enough.   But the rest of your comment changes to the Steady State configuration, which I at least am not yet using.   Also, I have found that the procedure you  describe, going to 'tools/internet options/delete under the browsing history, does not work; these long file names do not delete, and most do not do anything, whether open, move, copy, scan with, print (except for the couple I described above).   The only thing that works at all is to login as admin and delete the local copy of the mandatory profile, and relogin as the user. 

      I just made a new profile yet again, with a change in 'tools\internet options\advanced, and I checked the box 'delete TempIntFiles when browser is closed'.
    That did nothing, I am back to no logins again due to long file names in TempIntFiles.

    My next move is to Firefox.
    • Proposed as answer by bmittleider Monday, April 06, 2009 3:18 PM
    Friday, March 20, 2009 7:44 PM
  • Can anyone pinpoint a site/url that this happens? I have this same problem in some of my labs at our school using mandatory profiles. I see this after students have been on the computers and I can't recreate the problem. The only thing I have been able to do to fix it is log in as an admin, unlock the account and then apply the lock again. I want to recreate the problem on my testing machine so I can try to write a script that will remedy the problem. Any site that you know causes this will be helpful.
    Monday, April 06, 2009 3:20 PM
  • I could resolve this issue by installing UPHClean tool on the SteadyState client.

    *****************************************
    User Profile Hive Cleanup Service
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=1b286e6d-8912-4e18-b570-42470e2f3582

    Overview

    The User Profile Hive Cleanup service helps to ensure user sessions are completely terminated when a user logs off. System processes and applications occasionally maintain connections to registry keys in the user profile after a user logs off. In those cases the user session is prevented from completely ending. This can result in problems when using Roaming User Profiles in a server environment or when using locked profiles as implemented through the Shared Computer Toolkit for Windows XP.

    note: Windows SteadyState 1.0 was called as "Shared Computer Toolkit"

    *****************************************

    The temporary user profile (c:\users\restricteduser) should be deleted at logoff, but the delete process might fail.
    Having too long filename under profile folder causes such a problem.

    You can also download latest beta version of the UPHClean tool from following blog.

    http://blogs.technet.com/uphclean/default.aspx
    Friday, May 01, 2009 4:19 AM
  • I HAVE A PERMANENT SOLUTION!

    I've had this same issue and it's bothered me for a long time.  I had this happening on a daily basis.  The suggestions about logout scripts don't work.  Trying to find a website that causes this was impossible.  I did find a solution and it has worked now for about 6 months for me with no problems.  The solution is the User Hive Profile Clean Up Service BUT NOT version 1.6d which MS has listed on the download center!  YOU MUST USE THE BETA VERSION 2.0.49 to fix this problem.  It is hard to find because most things on the site I'm about to give you reference 2.0.48. Here is the link to 2.0.49: http://blogs.technet.com/uphclean/attachment/3145464.ashx (PS in the blog mentioned below, when you go to download the "new" version the link says that it is verion 2.0.48 but is is really 2.0.49.  Talk about confusing...like I really need this after all of my "file name too long" messages.  Does anything "just work" anymore?)

    Robin Caron is the person who wrote UPHClean.  She has a blog about it here: http://blogs.technet.com/uphclean/.  On her post about UPHClean V2.0 she mentions something that was liquid gold.  Here is an exerpt:

    Real World Problems with UPHCLEAN 1.6d and Windows XP in general

    Microsoft Internet explorer cookies and favorites files sometimes excide more than 255 chars and can only be deleted through the command line.

    Other symptoms of this is if the same user logs in again he or she gets a new profile with a name like username.000, username.001 etc.

    I actually had some hope for this problem when I read this so I downloaded it and tried Steady State 2.5 with Win XP and it fixed the problem.  I can't tell you how much I hated MS for allowing files with names longer than 255 to be created on the computer but not giving the OS the ability to DELETE the file that was just created.  It drove me CRAZY!

    The only thing I can't remember is the order I installed this new service.  I should have taken better notes but my guess is that I uninstalled Steady State, uninstalled the UPHClean 1.6d, restarted the pc.  Installed the UPHClean 2.0.49, Re-Installed Steady State.  I did this for my testing and it worked.  When I made a production quality image I installed windows from scratch.

    After running this image for about 6 months I haven't had any of those file name too long messages.  I have 400 public computers spread across a 200 mile radius...which reminds me...one of the suggestions was to unlock the account, go in and delete the temp files and then relock it again...OKKKK that would be insane for me and probably most others.

    Please let me know if this works for you!


    • Proposed as answer by Lockn Down SS Monday, May 04, 2009 5:13 PM
    Monday, May 04, 2009 4:23 PM
  • Thank you, Lockn Down SS, for your endorsement of the UPHClean Ver 2.0 Beta, in spite of the problems listed on the blog.

    I'd been battling clearing out temporary internet files for the past month because we no longer reboot PCs in-between library patrons. Clearing the cache is important to us because we don't want a user logging in to previous user's Yahoo email account (nightmare stories). I'd used it for years on Microsoft Shared Computer Toolkit and SS ver 2, but I just recently realized I didn't have UPHClean installed on my newest master image on our new PCs. 

    So I've installed ver 1.6d, but now I'm having the same problem described above by BeGr and Rob Elmer. I've seen the same thing on the older versions of SS also. It only happens occasionally. I'm in the habit of obsessively cleaning out the IE cache from the unlocked profile every time I make changes to the computer because of it, but that doesn't completely solve the problem. Now I see why -- the profile is not unloading completely.

    Additionally, when the error message comes up and you log off (pressing the shift key to get to ctrl+alt+del screen), the computer gets stuck on the ctrl+alt+del screen. In other words, when you do a ctrl+alt+del the computer auto-logs in to the profile! By itself. Strange. No opportunity to get back to admin. When rebooting doesn't clear up the problem I've had to reimage the machine, rather than continue troubleshooting.

    I'd seen references to the UPHClean upgrade, Version 2.0.48.0 (or rather, 2.0.49.0), and the blog in the SteadyState forum, but no glowing recommendations for the upgrade until now.

    Do you really believe that it is necessary to uninstall / reinstall SteadyState?

    I am going to try the new beta of UPHclean on 15 public computers at one library branch. I will try to get back to this forum with my results.



    PCC
    • Edited by PC Chris Friday, May 08, 2009 4:53 PM
    Thursday, May 07, 2009 11:13 PM
  • Well, I've tried it at one of our branches over the weekend and I am still getting reports of the error in BeGr's original post. I tried the logoff script and also had the PC hang for 10 minutes on logout. It does delete the temporary <username> profile, but it would be quicker just to reboot.

    One comment to Rob Elmer and those of you trying to clear the cache from the unlocked profile -- be sure to have your browser pointed to about:blank before you delete the files from tools | delete browsing history. Otherwise, if you have a page or tab open to a site that continually updates graphics on the page (like Everett Library's home page does), the temp files fill up again before you have time to close the browser.

    I will update all 15 PCs at the one library branch again, clearing the temp files like I just described. Just to be sure I have done it! Will check back later. I will also be contacting Robin Caron, creator of UPHclean.


    PCC
    Monday, May 11, 2009 4:35 PM
  • Hi,

     

    We occasionally see this with locked profiles.  When a profile is locked, Windows copies the original profile directory (often c:\users\user.orig) to a temporary location (often c:\users\user).  During the user's session, changes the user makes are written to this temporary location.  When the user logs off, Windows deletes the temporary profile, thus cleaning up his changes.

     

    When you see the warning about filenames being too long when the locked user logs in, the problem is usually that temporary internet files created by Internet Explorer exceed the default 260 character path length limit, so Windows encounters an error when it tries to copy these files to the temporary location.  It's possible that other applications could create long filenames/paths that cause similar problems.

     

    I've been able to solve the problem by unlocking the profile, logging in as the restricted user, then emptying the user's temporary internet files in Internet Explorer.  Then log off, log on as the Administrator again, and re-lock the user's profile.

     

    Hope that helps.

     

    -Rob

     

    Thanks Rob. Your solution works just fine.... it is simple to follow
    Monday, May 11, 2009 5:56 PM
  • Well, I just cannot get this. I have been a PC support tech for fourteen years now, and I've used every version of this product, from the Gates PAC tool to both versions of the Shared Computer Toolkit, SteadyState alpha, beta, public, and versions 1, 2 and 2.5 and I've still never seen anything so frustrating. We've been rebooting between users for about six years to circumvent the long-standing issue, but I'd like not to go back to that.

    My user profile, whether locked or unlocked, is as immaculate as can be. I have deleted and recreated profiles, used both versions of UPHclean etc etc. and am still having the same problem about once or twice a day on 25% of our computers at our two library branches.

    I heard back from the UPHclean support and Robin Caron, and they asked me to send event logs, which is nearly impossible when you can't even get into the admin profile unless you reboot, thereby clearing up the issue plus the event logs. But I did use both TightVNC (to remotely get to the login screen) and remote desktop (to get into admin) to capture the logs on a problematic machine. I sent them six pages of logs two weeks ago and haven't heard back.

    Meanwhile I have a dozen very uptight administrators and librarians waiting for a solution. So I'm going to have to force a reboot in-between users to circumvent this problem.

    Next I will try re-imaging with a pre-SteadyState, pre-UPHclean master image that has no profiles on it. I will then create the profile and not even launch the browser so there is no chance of temp, cookies or temporary internet files being kept. I will load Steadystate, lock the profile and report back with my results.

    If anyone has more ideas I would be glad to talk to you off-list. Please contact me right away.

    Chris Cooper
    Everett Public Library
    425-257-8039
    ccooper@ci.everett.wa.us
    PCC
    Friday, May 29, 2009 5:34 PM
  • In the 2 years that I've been working with SteadyState I'd never had this issue until I installed XP SP3. Thank you so much for your posting. It worked like a charm.

    April
    Wednesday, June 17, 2009 7:08 PM
  • pc.assist/April: would you mind sharing with us where you saw this discussion?
    PCC
    Wednesday, June 17, 2009 7:27 PM
  • Chris, I'm running into the same issues that you seem to be having.  I'm working in a school computer lab that uses a single mandatory (read only) roaming profile for the workstation machines.  Pretty randomly, they will run into this problem when the students log into the domain from the lab computers.  They get the error

    "Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile...etc".  They are logged on with a temporary profile and there is an error in the event log to the effect of Windows being unable to copy some file from the server (buried in the temp internet files of the mandatory profile on the server) because the filename or extenstion is too long. 

    This problem cropped up a few months ago, and to my knowledge, they never experienced it before.  It is pretty random as far as which computers have the problem and when it occurs.  Differen't computers, different users, different times.  As far as prevention goes, in your experience, does rebooting instead of logging off seem to stave off the issue?  I realize that option isn't necessarily a solution for you, but that would be enough of a fix for this computer lab.  Unfortunately, since the problem is so sporadic (and school is out), it is hard to test whether or not that will actually fix the problem.  I'm hoping to have this issue resolved before the next school year starts up!

    Thanks,
    Jeremy
    Monday, June 22, 2009 3:20 PM
  • Yes, rebooting clears it every time, because rather than just the profile being refreshed (by the profile lock/mandatory profile) Windows Disk Protection is refreshing the entire disk. When we have the error that's the only way to get it to go away. We've been rebooting for seven years, when we had our old PC Reservation system here at the library, because of this error and one other glitch. We didn't have as many glitches when we launched a brand-new system in April 2009 so we were hoping to avoid rebooting, because our library patrons feel the reboot cheats them by 3 or 4 minutes out of their "right" to 60 minutes a day (if you can believe that). The fewer the complaints and helping patrons reboot, the more we can focus on "real" reference questions.

    I have removed the Google toolbar at one of our branches to see if that's our problem. Google leaves behind massive crumbs including registry data. The next thing I will try, especially if pc.assist/April answers my query, will be to remove WinXPsp3. I will get back to the forum with my results, for those of you whose errors are not resolve by the techniques and software suggested above. Good luck.
    PCC
    Wednesday, June 24, 2009 3:35 PM
  • Sorry Chris, one more clarification.  Are you saying rebooting fixes the error after it occurs, or does rebooting between user logins prevent the error from happening?  The lab isn't using Steady State or anything else.  Just the single Mandatory Roaming Profile. 
    Thursday, June 25, 2009 12:03 PM
  • No problem at all.

    Automating a reboot in-between users every time prevents the error from happening at all, because the whole disk is restored every reboot. This is definitely the solution if you don't have impatient users waiting to logon, like we do.

    If you do not automate a reboot between users every time, theoretically just the profile is overwritten, which is where the problem lies. The profile is just not unloading correctly, according to the event logs. However, if you have your PCs set up to just logout/login like we do, when the error comes up -- maybe twice a week on every WinXPsp3 machine -- a manual hard reboot (holding the power button down until the power goes off) will at least get you back to square one, and back into the profile again. Again, this is because the whole disk is restored with a reboot.
    PCC

    Jeremy -- In regards to my explanation about "restoring" the disk, we are using SteadyState with Windows Disk Protection. Are you using the User Helper (or Hive) Cleanup Service, described above? If so, does it help or hinder the logoff/login process? I am torn about using it because we have different problems with it (e.g. this failure to load profile problem) or without it (e.g. failure to clear the cache).
    • Edited by PC Chris Thursday, June 25, 2009 6:40 PM
    Thursday, June 25, 2009 5:52 PM
  • Chris, the lab isn't using anything but the mandatory profiles.  We had thought about moving to something like Deep Freeze, but at this point, the only system to keep things "default" is simply using the read only mandatory profile.  The biggest thing to deal with in the lab are minor things like kids changing wallpaper, deleting icons, etc.  Since they are supervised, there isn't really as much of a need for a bigger guns.  Just something to keep the interface consistent on the machines so the lab teacher can teach and have everyone see the same things. 

    The mandatory profile actually did a good job with that until that error started cropping up.  The biggest issue is that when it occues, the mandatory profile doesn't load and the student gets a desktop that doesn't match what the teacher is teaching with.  As I mentioned earlier, since it is a classroom, and the kids are logging on / off at regular intervals, it isn't really a big deal for the teacher to just make sure they start rebooting instead of simply logging off.  I had thought about looking into the UHCS, but I'd rather not introduce another complication into the mix if the rebooting prevents the problem. 

    Good luck with it, and thanks for your help!

    Monday, June 29, 2009 1:23 PM
  • Thanks, Rob, your solution got me on the right track!  If you are unsure how to turn this into a permanent fix, I would suggest the following link:
    http://www.mvps.org/winhelp2002/delcache.htm

    Make sure your machine is upgraded to IE8.

    <!--StartFragment-->Login as an admin account and run a disk cleanup (make sure you choose to remove temp. internet files) and then unlock the restricted user's profile.  Then follow the steps on http://www.mvps.org/winhelp2002/delcache.htm in IE while still logged in as the admin user.  Once this is complete, try logging in as the restricted user.  This got me logging back in, but I have not seen if I will get locked out again after the limited user has been on the internet "playing around". 

    Good luck.  Hope this helps!

    -Alex

    Thursday, December 31, 2009 7:07 PM
  • Thanks for this answer!

    CESabarre Free Tech Support
    Bad News: There really is no such thing as Free Tech Support.
    Good News: Oftentimes a simple thank you is the best form of payment!
    Sunday, October 03, 2010 11:37 AM
  • I can tell you how to find the file from the command prompt

    you can use dir/s/a:h > hidden.txt

    this will make a text file with the complete path and filename's of all hidden folders and file's. hope it helps

    Sunday, October 21, 2012 5:56 PM
  • Try " Long Path Tool " is also useful in situations where you see these error messages: Cannot read from source file or disk, there has been a sharing violation, cannot delete file or folder, the file name you specified is not valid or too long, the source or destination file may be in use 
    and many other file managing errors that you encounter in your computing use.


    Thursday, August 01, 2013 2:24 PM
  • show hidden folders? :)

    maxim

    Tuesday, August 20, 2013 4:18 PM
  • With filename too long error I use "Long Path Tool" to get  fast and easy fix .
    Thursday, September 05, 2013 7:51 PM
  • Try Long Path Tool software for an easy fix.
    Monday, November 04, 2013 12:40 AM