Windows 7 64 bit - for one user cannot connect to domain - just get black screen and cursor
I have a user who has a recent Win7 64 bit build (RC Professional). It connected regularly to a Windows domain (Win2003) with no problem. Today the user tried to logon and the system hung after the logon credentials were entered and showed only a black screen with the cursor. The system can be shut down tidily by pressing the power button and then the screen returns showing Windows shutting down. If the PC is booted without being on the network it's fine (the user logs onto the local machine with their domain credentials) and once the boot is completed, we can reconnect the network cable and connect to network resources fine. But strangely another user on the same machine can logon fine. So I think the user has a corrupt profile but I really don't know what to delete or change to confirm this. Any ideas from anybody. I can't see anything on the local machine that has changed. There have been no Windows Update (it's disabled anyway by GP) and they didn't install any programs since it worked on a Friday afternoon but failed on a Monday morning. All users in our enviroment have local admin access on the domain to their own machines.
May 17th, 2010 11:29am

The RC is about to expire permanently. The user's system needs to have the full release (RTM) verwsion installed and you cannot "upgrade" from RC to RTM. Expiration Dates and functionality. Effective June 1, 2010, Windows 7 RC will expire. To continue using your computer, you should prepare to install the retail release version of Windows 7 or install an earlier version of Windows before the June 1, 2010 expiration date. You will be unable to upgrade from Windows 7 RC to the retail release version of Windows 7. However, you can back up or transfer your data to your next or previous operating system. Effective February 14, 2010, the expiration notification process begins: Windows 7 RC users receive an expiration notification in the task bar one time per day. Windows 7 RC users are presented with the Notification Wizard one time every four hours and then one time every hour. Effective March 1, 2010, Windows 7 RC enters the next phase of expiration: Expiration notifications in the task bar continue. Computers that are running Windows 7 RC restart every two hours. Effective June 1, 2010, Windows 7 RC expires: Windows starts to a black desktop. Windows 7 RC users are presented with a Windows Activation screen. The screen states that the Windows that you are running is not genuine. Computers that are running Windows 7 RC restart every two hours. For more information about how to uninstall Windows 7 and revert to your original operating system or another version of Windows 7, click the following article number to view the article in the Microsoft Knowledge Base, How to uninstall Windows 7. Reference: Description of Windows 7 Beta and Windows 7 Release Candidate (RC) expiration dates and functionality
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2010 1:32pm

On Mon, 17 May 2010 10:32:28 +0000, Rick Dee wrote: > The RC is about to expire permanently. The user's system needs to have the full release (RTM) verwsion installed and you cannot "upgrade" from RC to RTM. It is not true that you can not upgrade from RC to RTM. You do *not* have to do a clean installation. Upgrading from RC to Windows 7 RTM is not supported and Microsoft advises against upgrading from Windows 7 RC to Windows7 RTM. However it *can* be done, by using a very simple workaround. You can read about it here http://www.intowindows.com/how-to-upgrade-windows-7-rc-to-rtm/ or on several other web sites that can be found by doing a search. Be aware that there is undoubtedly some risk in doing this. However I can tell you that my personal experience with doing the upgrade has been very good, and I had no problems with it or with its results. So, here's my advice: Try the upgrade using the workaround above, since it's much less work than doing a clean installation and reinstalling and reconfiguring all your programs. However, be aware of the risk in doing this, and be prepared to do a clean installation if the upgrade creates problems for you. Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003 Ken Blake
May 17th, 2010 9:40pm

I am surprised that a Microsoft Most Valued Professional (MVP) would recommend to a customer an unconventional and not recommended hack to upgrade from RC to RTM. I think Microsoft should consider revoking your MVP designation for such an action!
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2010 12:10am

My fault. I mean the RTM. We are not running the RC at all. THis is an OEM version provided by HP as part of the free upgrade from Vista. I saw that the first time a user logged onto the machine it worked but subsequenAnyway since then I solved the problem but not sure why. We were finding that all our XP users were having problems in that the logon scripts were not working for them (stored in \\fileserver\netlogon) We dug around and saw this setting in the registry. HKLM\Software\Microsoft\Windows NT\Current Version\Profilelist\<profile id>\RunLogonScriptSync which was set to 1. We used GP to force this value to 0 and then the machine logged on okay and the XP machine also now invoked the logon scripts. Prior to that, noting that the first time a user logged onto a machine it worked, I deleted this registry key for that user. He then could logon okay but after logging off, next time he logged on it hung. We then tried moving the machine out of the OU for the organisation and into a OU for general computers where no logon scripts would run. This time the machine would hang for about 8-10 minutes and then logon - hardly satisfactory. It was then we saw the registry entry noted above, changed it and it worked. Not entirely sure what we did and why it worked but we are not arguing with success!
May 18th, 2010 10:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics