July 2012 security updates for Microsoft Windows, Microsoft Office, Microsoft Developer Tools, Microsoft Server Software, and Internet Explorer. We use Windows local area network and the Windows 7 pro workstations which are connect to Windows Active Directory. There is Windows 2008 and Windows 2003 server domain controllers file servers and application servers in our Active Directory. We are using basic Active Directory services like DNS, DHCP, file and print services. Microsoft WSUS Server pulls automatically critical and important windows security updates to Windows 7 pro workstations. When the new Windows security updates (July 2012) were installed to Windows pro 7(fi) workstations so couple of Windows 7 pro workstations could not to log on Windows with Windows Active directory normal domain user account. Windows 7 pro workstation get stuked when log in to Windows. I can log in with a Windows 7 local administrator account to Windows. When I remove the new installed windows security updated (July 2012) or I restore Windows 7 Pro using Windows restore function to restore point before (July 2012) security updates was installed, then I can again log on to Windows like normally with normal Windows Active Directory normal domain user account. What/ or which Windows security updates does cause the this Windows 7/ "Windows domain log on problem"? and how the problem is fixed? Reards, Marko

Hi, I have exactly the same but with Windows 7 Yltimate. Need desperatly an answer/solution. Dirk

Hi, What kind of error message did you receive? Please post the specific error here. If you delete the old user profiles, and try to log on, can you successfully log on to the computer?Juke Chou TechNet Community Support

Hi, What kind of error message did you receive? Please post the specific error here. If you delete the old user profiles, and try to log on, can you successfully log on to the computer?Juke Chou TechNet Community Support

Hi Guys i'm experiencing the same problem as above on my windows 7 Network, If i rename or remove the old user Profiles, the next user to log on then gets a TEMP profile, Please help

I also experienced the problem described. The message I received is the Windows logged me in using a temporary profile. In order to resolve this I had to delete the user profile from %computername%\Users\<profile>. Just doing this doesn't totally resolve the problem. Next step that worked for me was to open Regedit and browse to HMLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList Once there I found the profile I was having trouble with by clicking on the GUID of each profile and looking at the ProfileImagePath which told me which profile the GUID was corresponding to. Once I found my trouble profile I deleted that GUID folder and rebooted. Upon logging back in with the profile I had trouble with it logged in correctly and not using a temp profile. Any idea which update may be causing this?Derek Larson

looks like its KB2709162