Conectare
 
Pagina de pornireBibliotecăInformațiiFişiere de descărcatSuportComunitateForumuri
Resurse pentru profesionişti IT >
> 
> 
Windows 7 SP1 upgrade corrupted all local user profiles

Answered Windows 7 SP1 upgrade corrupted all local user profiles

  • 2 martie 2012 20:58
     
     
    Sign in pentru a vota
    0
    I am not using roaming profiles.  All profiles are local.  One computer with Windows 7 x64 was upgraded to SP1 on 2/29/2012.  Since the install, it corrupted all of the user profiles.  I used WSUS to push out this Service Pack.  Now when I try to login with any user that hasn't logged into the machine, they are getting temp profiles.  I tried to research this on and on, but cannot find anything due to the SP1 upgrade.  Can you please help?
     

Toate mesajele

  • 2 martie 2012 21:04
     
     
    Sign in pentru a vota
    0

    You can fix the corrupted profiles by going through this process

    http://windows.microsoft.com/en-US/Windows7/Fix-a-corrupted-user-profile

    And go through as well.

    http://support.microsoft.com/kb/947215

     
  • 2 martie 2012 21:13
     
     
    Sign in pentru a vota
    0
    I guess my question would be why did doing the SP1 upgrade along with a .net 4 client profile upgrade corrupt the user profiles?
     
  • 2 martie 2012 21:14
     
     Răspuns
    Sign in pentru a vota
    0
    To be honest the upgrade shouldn't have corrupted the profiles but either updates possibly could have corrupted the profiles or something else. I really can't tell you why or what actually did the corruption. 
     
  • 2 martie 2012 21:16
     
     
    Sign in pentru a vota
    0
    Anyway I can drill down to find out why they got corrupted?  I checked the event viewer for the 29th since all the profiles had the same timestamp that date and I couldn't find anything.
     
  • 2 martie 2012 21:19
     
     
    Sign in pentru a vota
    0
    Hate to say there is nothing out there that I can think of that will tell you why they got corrupted. 
     
  • 2 martie 2012 21:21
     
     Răspuns
    Sign in pentru a vota
    0
    Ok thanks!  I guess I was just concerned over if the .net 4 client profile update had anything to do with it as well.  I'm wondering if it is also due to our imaging department not syspreping the machines before deployment.
     
  • 2 martie 2012 21:29
     
     
    Sign in pentru a vota
    0
    That possibly could have caused the issue as well
     
  • 10 octombrie 2012 22:27
     
     
    Sign in pentru a vota
    0

    I had same thing happen to me. My systems were syspreped so i dont think its that although you could run into other issues because of that. Im still trying to figure out why.