Today I installed Windows 7 RC 1 x86 on my test desktop (replacing W7 Beta) everything was going great till I joined the domain. After joining the domain I receive the following on login...Pictureexplorer.exe - Application ErrorThe application was unable to start correctly (0xc0000005). Click OK to close the application.And nothing... If I hit Ctrl+Alt+Del I have a few options. "Start Task Manager" returns the exact same error as above except explorer.exe is replaced with taskmgr.exe. All the other option do work however. (I can lock the computer, switch users, Log Off, Change Password). Starting up in safe mode works correctly, but Im not able to disjoin the machine from the domain, because a required service isnt running.I had installed McAfee 8.7i on my desktop so to rule that out as an issue I spun up a VM with W7 RC1. Doing nothing with it after the install completed I joined our domain and after reboot was greeted with the same errors as my physical desktop. I also have a VM with W7 Beta that is a member of our domain without issue.We are a Windows 2000/2003 domain established about 9 years ago. I tested Vista (Beta/RC/Release)against this domain without issue. We have multiple polices and who knows what else associated with this domain. Thanks in advance,Justin

I booted into Safe Mode with Network Support and was able to put the machine back in a workgroup. I'm now able to login without issue. Any idea why I'm unable to login to the box when joined to our domain?

Joing the machine back to the domain makes the error above come back. Looking at the event logs the only thing that looks funning is this...Event 4373 NtSevicePackThis error apears on both my desktop and VM and only when joined to the domain. Currently running an EventComb to see if I can see anything funny on that end.

I am having the same issue. We have installed windows 7 rc on a couple of different computers as well as in a virtual pc. Works fine until we join it to the domain. Once joined to the domain we get the same error as above even in safe mode.

I have this same exact issue, everything was fine until I joined the domain. If I remove it from the domain it will start working again. Explorer, wscript, taskmgr all faill with 0xc0000005.

Same problem...out of curiosity do you have a login script for users on your domain? I filed a bug on connect, we might get feedback quicker there. Running under safe mode, I'm able to login and access domain resources. I'm thinking itMIGHT be the computer browser.https://connect.microsoft.com/windows7/feedback/ViewFeedback.aspx?FeedbackID=441701Keep your head in the Clouds as you're coding .NET http://azurecoding.net

Putting the computer account in an OU with GPO inheritance disabled has solved this issue for me.That's strange I was using the Beta with our domain's GPO appliedwithout any problem.Anyway it seems to be due to a GPO. I will try to isolate it and keep you informed.

We run a VB script at logon. I'm going to try removing it from my user profile to see if it quits happening. Unfortunately there are no OUs which do not have some level of GPO inheritance to place my desktop that I have access to move the object to, so I cannot test this theory.

Turned out to be the Required Installs Policy for us..Keep your head in the Clouds as you're coding .NET http://azurecoding.net

For testing you should deny the rights to your Windows 7 computer account on the policy containing the script.So the policy will not apply.

I created a new OU and told it not to inherit any policies. Putting the Windows 7 computer inthe OU with no policies I'm able to join the domain and login. Wehave 3 policies and I have been able to reapply 2 without issue. Adding the 3rd policy causes the problem. I believe thepolicy causing the problem "injects" Domain Admins in the local machines administrators group so we can access machines on our domain. It also has some file restrictions associated with avirus that we got a few month back that McAfee wasn't detecting properly. These restriction were setup during a Microsoft support call.Bottom line it's working... THANKS!

I'm having problems joining my Win 7 RC1 x86 computer to a Active Directory domain. The GPO did not work as expected, but I have yet to check the script. Removing the computer from the domain hung and required a forced power down. Ray

Same problem here. Also confirmed that putting the Windows 7 machine into an OU with all policies blocked fixes the problem. Will work on isolating the issue. My hunch is something to do with the domain admins being added to local admin group. This wan't a problem with the beta test systems we ran.

Hi,I am not an admin and was wondering if there is anything I can do on the local machine to make it work on the domain at work? The beta builds were fine but RC1 has this issue.Saves me going back to the beta build

According to the response on my submission it has been addressed in a later build.Keep your head in the Clouds as you're coding .NET http://azurecoding.net

I am running W7RC and added it to our domain (DC Server 2000) without issues. We have a few GPO's but nothing caused any interference with joining the domain. The place where things got a little strange is once I logged into the domain on that machine as admin, in the user accounts I could not add any other domain profiles into the system. WhenI treidI would get an error stating that the trust from the W7RC machine and the domain controller was broken. I found if I logged in as a specificuser profile it would let that domain profile log in and then it recognized that account but not until then. Once recognized I could set the profile access rights with no problem (admin, power user,etc.). In XP all I would do is log in as admin and add all other profiles required for that computer at one time in the user account mangement area. Then I did another test connecting to the W7RC machine from my main XP SP2pc using the computer management tool.I was able to add any user profiles in our AD to any access level without issue. This is kind of strange overall and it would be nice if this were fixed before the final W7 is released in Oct. 2009.

How do we get a later build? I just downloaded the iso today and it's still build 7100 (64bit). Do you have a link to where we may be able to get that build? Thanks!!

I just experienced the same thing and yes, removing all GPOs and blocking inheritance resolved the issue. Does anyone know if there actually is a new build that resolved this issue? Thanks!