MSFN Forums > Server Execution Failed (Windows Explorer is Not Responding)

Full Version: Server Execution Failed (Windows Explorer is Not Responding)

MSFN Forums > Microsoft Software Products - Discussion & Support > Windows Vista

lukenuske

Jun 6 2007, 01:36 AM

Hey,

I am having serious problems with my Network Settings in Vista. I am running Windows Vista Home Premium 64-bit

Basically whenever I boot up, a little red X appears in my bottom right corner. The computer says that Server Execution Failed and that my connection status is unknown. But wait it gets better. If I go into Network and Sharing Centre I get no response from the computer and the window completely freezes. Ctrl+F4 does nothing, closing the window doesn't work. So, I open Windows Task Manager and end the process. At this point the computer responds with Windows Explorer is Not Responding. The weird thing is my network is working perfectly. I can surf the net, talk to my Xbox 360, etc

I have downloaded a 'fix' for this from the Microsoft website but it hasn't worked.

Further, I read somewhere that if you have multiple Default Gateways set then the Server Execution Error may come up if the adapter cannot talk to both addresses. Now this is a possibility as I recently tried to setup a wireless router that used a separate address. Unfortunately I cannot change this because every time I go into Network and Sharing Centre I get given the pleasant message of Windows Explorer is Not Responding.

Is it possible I've been hacked?

I just don't know - Any suggestions would be fantastic!

Cheers,

Luke

fizban2

Jun 7 2007, 11:13 AM

if you boot into safe mode do you get the same error when loading the network center? try booting into safe mode with networking and see if you get the same error

cluberti

Jun 8 2007, 11:59 PM

I agree - does it happen in safe mode w/ networking, and also, if you disable one or the other adapter (try disabling each, one at a time and reboot), does the issue occur? This sounds like a driver issue, honestly, because if it were a Vista issue we'd (for sure!) be hearing more about this one.

lukenuske

Jun 9 2007, 02:11 AM

Hey Guys,

Thanks for the suggestion, I didn't even think of booting in safe mode. Unfortunately it didn't help. Vista still hangs when I go into Network and Sharing Centre and I have to end the program through Task Manager. I have attached a screendump.
Maybe the forum will be hearing more about this problem?

Cheers,

Luke

cluberti

Jun 9 2007, 07:48 AM

Would you be able to dump the box the next time it hangs?

http://www.msfn.org/board/Creating_memory_dumps_t90244.html

khem

Jul 16 2007, 01:25 AM

Not sure if I should be starting a new thread or posting here, but I have been having the same problems. I am running duel core AMD 32 and Vista Home Premium. If I made a mem dump by using the task manager and right clicking Network Sharing Centre when it hangs, would this give me the correct output to post for someone to help me with this ? thanks for any help

khem

Jul 16 2007, 07:48 PM

Still haven't been able to track down the problem. I am including dump files of the stalled process as per cluberti's instructions. Hope someone can get me on the right track.

Thanks for any help... Kevin

cluberti

Jul 16 2007, 09:48 PM

Ah - I see the problem. From the log:

CODE

*** ERROR *** *** ERROR *** *** ERROR *** The following requested processes are not executing: EXPLORER;

Consider using the .exe the next time you run it

cscript adplus.vbs -hang -pn explorer.exe -o c:\adplus

khem

Jul 16 2007, 11:28 PM

Thanks,

Not sure what I am looking for, The 'Control Panel\ Network and Sharing Center' is freezing

cluberti

Jul 16 2007, 11:50 PM

Please don't post 250 lines in a thread - some people still use modems to look at this board.

Anyway, thread 27 is the likely culprit for the hang:

CODE

27 Id: ee4.1134 Suspend: 1 Teb: 7ff9d000 Unfrozen
ChildEBP RetAddr Args to Child
08b4e048 762dafb9 752413ff 08b4e0cc 00000000 ntdll!KiFastSystemCallRet
08b4e04c 752413ff 08b4e0cc 00000000 000003e0 USER32!NtUserRealInternalGetMessage+0xc
08b4e088 752416f6 08b4e0cc 00000000 000003e0 DUser!CoreSC::xwProcessNL+0xf5
08b4e0ac 762daff1 08b4e0cc 00000000 000003e0 DUser!MphProcessMessage+0x33
08b4e0f4 77980e6e 08b4e10c 00000014 08b4e1b8 USER32!__ClientGetMessageMPH+0x30
08b4e11c 762dc5b4 762dc573 08b4e1ec 00000000 ntdll!KiUserCallbackDispatcher+0x2e
08b4e120 762dc573 08b4e1ec 00000000 000003e0 USER32!NtUserPeekMessage+0xc
08b4e148 762dc5cd 08b4e1ec 00000000 000003e0 USER32!_PeekMessage+0x74
08b4e174 76a16449 08b4e1ec 00000000 000003e0 USER32!PeekMessageW+0xfa
08b4e1c8 76a163fe 08b4e1ec 00000000 000003e0 ole32!CCliModalLoop::MyPeekMessage+0x30
08b4e208 76a167be 08b4e3ac 0230c328 00000000 ole32!CCliModalLoop::PeekRPCAndDDEMessage+0x30
08b4e21c 76a2d001 08b4e23c 000003e8 08b4e24c ole32!CCliModalLoop::BlockFn+0x62
08b4e244 76b1802c ffffffff 0230c328 08b4e350 ole32!ModalLoop+0x5b
08b4e260 76b19984 00000000 08b4e364 00000000 ole32!ThreadSendReceive+0x12c
08b4e288 76b197f0 08b4e350 01ad0e20 08b4e3ac ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0x194
08b4e368 76a2d0a7 01ad0e20 08b4e524 08b4e474 ole32!CRpcChannelBuffer::SendReceive2+0xe7
08b4e384 76a2d059 08b4e524 08b4e474 01ad0e20 ole32!CCliModalLoop::SendReceive+0x1e
08b4e3fc 76a44bdb 01ad0e20 08b4e524 08b4e474 ole32!CAptRpcChnl::SendReceive+0x73
08b4e450 76471dd0 01ad0e20 08b4e524 08b4e474 ole32!CCtxComChnl::SendReceive+0x1c5
08b4e468 76471d87 0038070c 08b4e57c 76471f58 RPCRT4!NdrProxySendReceive+0x43
08b4e474 76471f58 e01a6075 08b4e998 070001f3 RPCRT4!NdrpProxySendReceive+0xc
08b4e95c 76471d64 76a382f0 76a3f09e 08b4e998 RPCRT4!NdrClientCall2+0xbde
08b4e980 763f3763 08b4e998 00000004 08b4ea00 RPCRT4!ObjectStublessClient+0x6f
08b4e990 76a13820 0038070c 00000000 08b4ee54 RPCRT4!ObjectStubless+0xf
08b4ea00 76a138f5 08b4ee54 08b4f3c4 00000000 ole32!CRpcResolver::CreateInstance+0x195
08b4ec5c 76a37021 76b1e4bc 00000000 08b4ee54 ole32!CClientContextActivator::CreateInstance+0x11f
08b4ec9c 76a36f49 08b4ee54 00000000 08b4f3c4 ole32!ActivationPropertiesIn::DelegateCreateInstance+0x108
08b4f478 76a4dbc7 6a92e7c4 00000000 00000004 ole32!ICoCreateInstanceEx+0x403
08b4f4d8 76a4de0a 6a92e7c4 00000000 00000004 ole32!CComActivator::DoCreateInstance+0xd9
08b4f4fc 76a4ddc3 6a92e7c4 00000000 00000004 ole32!CoCreateInstanceEx+0x38
08b4f52c 6a9785ca 6a92e7c4 00000000 00000004 ole32!CoCreateInstance+0x37
08b4f57c 6a979354 08b4f59c 08b4f598 08b4f5a0 netcenter!MiniMap::_GetNetworkStatus+0x4d
08b4f5a4 6a92fdb4 00000001 0303dab0 6a9393ff netcenter!MiniMap::UpdateStatus+0x1d
08b4f5b0 6a9393ff 08a6eeeb 0303db34 0303dab0 netcenter!CSNOCplCore::NotifyMiniMap+0x29
08b4f5f0 6a939b09 6a9127ec 6a97e000 0303dab0 netcenter!CSNOCplCore::HandleConnectivityChange+0x311
08b4f60c 6a93c157 08b4f6bc 000708ce 00000000 netcenter!CSNOCplCore::Refresh+0x109
08b4f620 6a93c93d 000708ce 00008001 00000000 netcenter!CMessageWindow::v_WndProc+0x337
08b4f640 762e1a10 000708ce 00008001 00000000 netcenter!CMessageWindow::s_WndProc+0x28
08b4f66c 762e1ae8 6a93c915 000708ce 00008001 USER32!InternalCallWinProc+0x23
08b4f6e4 762e2a47 00000000 6a93c915 000708ce USER32!UserCallWinProcCheckWow+0x14b
08b4f748 762e2a98 6a93c915 00000000 08b4f794 USER32!DispatchMessageWorker+0x322
08b4f758 7268b8fa 08b4f770 00000003 00000000 USER32!DispatchMessageW+0xf
08b4f794 7268cb0b 00000000 00000000 02f0e268 BROWSEUI!CBrowserFrame::FrameMessagePump+0x14f
08b4f7a8 7268cc90 02f47b78 00000000 00000000 BROWSEUI!BrowserThreadProc+0x5e
08b4f7c0 76223833 02f47b78 08b4f80c 7795a9bd BROWSEUI!BrowserNewThreadProc+0x43
08b4f7cc 7795a9bd 02f47b78 08b43eb9 00000000 kernel32!BaseThreadInitThunk+0xe
08b4f80c 00000000 7268cc4d 02f47b78 00000000 ntdll!_RtlUserThreadStart+0x23

Would you be able to actually provide the .dmp file here, or put it somewhere we can download it, to see what this thread is actually doing? Please put it somewhere we can analyze it - I'm not asking because it's nice to have, it's necessary to be able to walk the .dmp file to figure this out.

gosh

Jul 17 2007, 01:48 PM

I dont know anything about vista, but this is what i would do. Since it's a network issue, i would suspect NIC drivers. I would disable the nic in devman and see if that works. I would update the NIC drivers. Sounds like a corrupt registry key. I would look at setupapi.log to see what is being logged. I would use regmon to see what registry keys are being accessed. I would make a new user account and see if that works, which would point to a current hkcu registry hive. I would run sfc /scannow if vista has that. i would reinstall the network stack, but i dont know the inf's in vista. It sounds like a reinstall might fix it, it might be deep registry curruption that would be hard to fix. Of course, uninstall anyting that doesnt the inet, such as download managers, web enhancers, crap like that.

-gosh

khem

Jul 17 2007, 06:27 PM

Thanks gosh I will try what you have sugested, will take some time as i am not sure how to do some of that so I have a learning curve.

I have a link to the dump file of explorer but it's 250mb, I need a way to narrow this down. (Wiping and reinstalling is starting to look like the easy way out) sorry about the lenghth of the earlier post wont happen again. I will update if i make any progress. Thanks for the help.

http://khem.files-upload.com/378366/PID-38...2007-0.dmp.html

fizban2

Jul 18 2007, 02:53 PM

defiantly sounds like a driver issues. Seeing as netowrking works fine until he trys to get into Network Center, then the driver is hanging because it can't either call some property that required or it isn't there. looking at the dump would be the best way to find the culprit (at least fastest)

guess i get another one to try out.

cluberti

Jul 19 2007, 08:41 AM

It looks like thread 27 is indeed where we're hung, but from the explorer dump we can't tell for certain exactly why - we're talking to a COM object that is out-of-process in a service host process:

CODE

0:027> kb
ChildEBP RetAddr Args to Child
08b4e048 762dafb9 752413ff 08b4e0cc 00000000 ntdll!KiFastSystemCallRet
08b4e04c 752413ff 08b4e0cc 00000000 000003e0 user32!NtUserRealInternalGetMessage+0xc
08b4e088 752416f6 08b4e0cc 00000000 000003e0 duser!CoreSC::xwProcessNL+0xf5
08b4e0ac 762daff1 08b4e0cc 00000000 000003e0 duser!MphProcessMessage+0x33
08b4e0f4 77980e6e 08b4e10c 00000014 08b4e1b8 user32!__ClientGetMessageMPH+0x30
08b4e11c 762dc5b4 762dc573 08b4e1ec 00000000 ntdll!KiUserCallbackDispatcher+0x2e
08b4e120 762dc573 08b4e1ec 00000000 000003e0 user32!NtUserPeekMessage+0xc
08b4e148 762dc5cd 08b4e1ec 00000000 000003e0 user32!_PeekMessage+0x74
08b4e174 76a16449 08b4e1ec 00000000 000003e0 user32!PeekMessageW+0xfa
08b4e1c8 76a163fe 08b4e1ec 00000000 000003e0 ole32!CCliModalLoop::MyPeekMessage+0x30
08b4e208 76a167be 08b4e3ac 0230c328 00000000 ole32!CCliModalLoop::PeekRPCAndDDEMessage+0x30
08b4e21c 76a2d001 08b4e23c 000003e8 08b4e24c ole32!CCliModalLoop::BlockFn+0x62
08b4e244 76b1802c ffffffff 0230c328 08b4e350 ole32!ModalLoop+0x5b
08b4e260 76b19984 00000000 08b4e364 00000000 ole32!ThreadSendReceive+0x12c
08b4e288 76b197f0 08b4e350 01ad0e20 08b4e3ac ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0x194
08b4e368 76a2d0a7 01ad0e20 08b4e524 08b4e474 ole32!CRpcChannelBuffer::SendReceive2+0xe7
08b4e384 76a2d059 08b4e524 08b4e474 01ad0e20 ole32!CCliModalLoop::SendReceive+0x1e
08b4e3fc 76a44bdb 01ad0e20 08b4e524 08b4e474 ole32!CAptRpcChnl::SendReceive+0x73
08b4e450 76471dd0 01ad0e20 08b4e524 08b4e474 ole32!CCtxComChnl::SendReceive+0x1c5
08b4e468 76471d87 0038070c 08b4e57c 76471f58 rpcrt4!NdrProxySendReceive+0x43
08b4e474 76471f58 e01a6075 08b4e998 070001f3 rpcrt4!NdrpProxySendReceive+0xc
08b4e95c 76471d64 76a382f0 76a3f09e 08b4e998 rpcrt4!NdrClientCall2+0xbde
08b4e980 763f3763 08b4e998 00000004 08b4ea00 rpcrt4!ObjectStublessClient+0x6f
08b4e990 76a13820 0038070c 00000000 08b4ee54 rpcrt4!ObjectStubless+0xf
08b4ea00 76a138f5 08b4ee54 08b4f3c4 00000000 ole32!CRpcResolver::CreateInstance+0x195
08b4ec5c 76a37021 76b1e4bc 00000000 08b4ee54 ole32!CClientContextActivator::CreateInstance+0x11f
08b4ec9c 76a36f49 08b4ee54 00000000 08b4f3c4 ole32!ActivationPropertiesIn::DelegateCreateInstance+0x108
08b4f478 76a4dbc7 6a92e7c4 00000000 00000004 ole32!ICoCreateInstanceEx+0x403
08b4f4d8 76a4de0a 6a92e7c4 00000000 00000004 ole32!CComActivator::DoCreateInstance+0xd9
08b4f4fc 76a4ddc3 6a92e7c4 00000000 00000004 ole32!CoCreateInstanceEx+0x38
08b4f52c 6a9785ca 6a92e7c4 00000000 00000004 ole32!CoCreateInstance+0x37
08b4f57c 6a979354 08b4f59c 08b4f598 08b4f5a0 netcenter!MiniMap::_GetNetworkStatus+0x4d
08b4f5a4 6a92fdb4 00000001 0303dab0 6a9393ff netcenter!MiniMap::UpdateStatus+0x1d
08b4f5b0 6a9393ff 08a6eeeb 0303db34 0303dab0 netcenter!CSNOCplCore::NotifyMiniMap+0x29
08b4f5f0 6a939b09 6a9127ec 6a97e000 0303dab0 netcenter!CSNOCplCore::HandleConnectivityChange+0x311
08b4f60c 6a93c157 08b4f6bc 000708ce 00000000 netcenter!CSNOCplCore::Refresh+0x109
08b4f620 6a93c93d 000708ce 00008001 00000000 netcenter!CMessageWindow::v_WndProc+0x337
08b4f640 762e1a10 000708ce 00008001 00000000 netcenter!CMessageWindow::s_WndProc+0x28
08b4f66c 762e1ae8 6a93c915 000708ce 00008001 user32!InternalCallWinProc+0x23
08b4f6e4 762e2a47 00000000 6a93c915 000708ce user32!UserCallWinProcCheckWow+0x14b
08b4f748 762e2a98 6a93c915 00000000 08b4f794 user32!DispatchMessageWorker+0x322
08b4f758 7268b8fa 08b4f770 00000003 00000000 user32!DispatchMessageW+0xf
08b4f794 7268cb0b 00000000 00000000 02f0e268 browseui!CBrowserFrame::FrameMessagePump+0x14f
08b4f7a8 7268cc90 02f47b78 00000000 00000000 browseui!BrowserThreadProc+0x5e
08b4f7c0 76223833 02f47b78 08b4f80c 7795a9bd browseui!BrowserNewThreadProc+0x43
08b4f7cc 7795a9bd 02f47b78 08b43eb9 00000000 kernel32!BaseThreadInitThunk+0xe
08b4f80c 00000000 7268cc4d 02f47b78 00000000 ntdll!_RtlUserThreadStart+0x23

Knowing that the class ID for the COM object is netman from looking at the CComActivator function, and that the netcenter GetNetworkStatus function is talking to dll netprofm.dll, we're talking to the service host that contains the Network List Service service:

CODE

0:000> u netprofm!CImplINetworkListManager::EnumNetworks
netprofm!CImplINetworkListManager::EnumNetworks:
6dc826fd 8bff            mov     edi,edi
6dc826ff 55              push    ebp
6dc82700 8bec            mov     ebp,esp
6dc82702 51              push    ecx
6dc82703 53              push    ebx
6dc82704 56              push    esi
6dc82705 57              push    edi
6dc82706 a10030cb6d      mov     eax,dword ptr [netprofm!WPP_GLOBAL_Control (6dcb3000)]

At this point, the problem is outside of the netcenter window, and likely in COM (or the Network List Service isn't running at all, however I do doubt that).

@lukenuske - Can you get a complete dump of your Vista box the next time you are able to make this happen? You can configure your machine to dump via the keyboard if you have a PS/2 keyboard attached to the box, by following these instructions:

1. Create or set the following registry value:
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
Value: CrashOnCtrlScroll
Type: REG_DWORD
Data: 1

2. Right-Click on the "My Computer" icon on the desktop and select "Properties", then click the "Advanced System Settings" link. On the "Advanced" tab, click "Settings" under the "Performance" header. Click the "Advanced" tab, then click "Change" under "Virtual Memory". Set the pagefile to be located on the partition where the OS is installed, and set it to be equal to Physical RAM + 50 MB.

3. Also in the "System Properties" window on the "Advanced" tab, click the "Settings" buttun under the "Startup and Recovery" header. Make sure "Complete Memory Dump" is selected (see 3a if this is not in the list). You can change the location of the memory dump file to a different local partition if you do not have enough room on the partition where the OS is installed.

3a. If the "Complete Memory Dump" option in step 3 is not available, you will need to manually set this registry value:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
Value: CrashDumpEnabled
Type: REG_DWORD
Value: 1

4. You will need to reboot for these changes to take effect.

5. The next time that your Network and Sharing center hangs, wait about 10 seconds and then hold down the RIGHT CTRL key and press the SCROLL LOCK key twice to cause the machine to bugcheck and create a memory dump. After the box comes back up, you'll find the resulting memory dump file in %systemroot%\memory.dmp that can be analyzed.

khem

Jul 21 2007, 07:04 PM

Sorry tried what you ask just havn't been able to lean how to set the registry values let alone find how to get the key combination you sugested on this HP Pavilion laptop dv9205ca. If you could point me towards a good place to learn about setting / writing registry commands I would appritiate it.

I did find this http://www.dumpanalysis.org/blog/index.php...ggers-on-vista/ and it looks like what I need but it will only give results when a crash occurs? I will keep learning about the registry. Thanks for all the help

biglickwid

Jul 27 2007, 03:45 AM

Here's the fix.

1. Right click "Computer"
2. Click "Manage"
3. Under the "System Tools" section, Double click "Local Users and Groups"
4. Click "Groups"
5. Right click "Administrators"
6. Click "Add to group..."
7. Click "Add"
8. Click "Advanced"
9. Click "Find Now"
10. Double click "Local Service"
11. Click "Ok" - NT Authority\Local Service" should show up in the list now
12. Click "Ok"
13. Close Computer Management and reboot.

Thanks to BlueShot @ Microsoft TechNet Forums

cluberti

Jul 27 2007, 11:06 AM

You do realize you're opening your box up to security compromise by doing that, correct? Giving a very, very specific and limited account global admin access?

khem

Jul 27 2007, 10:45 PM

I think I figured out how to get the dump file, hope it has the correct information. Have been having no luck uploading the dump file that was named Memeory.dmp changed it to Memorydmp and will try that. The file continues to stall while uploading or look like it has completed the upload and never shows. That's what i get for using free services. I hope changing the name like this won’t corrupt the file and make it unusable?

Thanks for the continued feedback

khem

Aug 1 2007, 08:40 PM

I was finally succesful in uploading a memory dump (155mb) of the 'Control Panel\ Network and Sharing Center' freezing.

http://www.orbitfiles.com/download/id1682957974

thank you for all the help.

cluberti

Aug 1 2007, 08:52 PM

QUOTE (khem @ Aug 1 2007, 10:40 PM)

I was finally succesful in uploading a memory dump (155mb) of the 'Control Panel\ Network and Sharing Center' freezing.

http://www.orbitfiles.com/download/id1682957974

thank you for all the help.

I only see this:

"File not shared"

khem

Aug 1 2007, 10:13 PM

sorry think I have the share woring now.

BL6ZiNx6iRL

Dec 12 2007, 04:34 PM

I hate to bump a Six(6) month old topic but I'm having this same problem. My internet runs fine and I'm able to browse the web, play online games, etc. But there's a little Red X on the Internet connection icon in the Lower Right corner. It was never like that before until a few weeks ago maybe like a month and a half. I originally ignored it since my internet was working and everything so I figured it was nothing. Then I started to think maybe it'll lead to bigger problems. It said something about DNS when I clicked on the icon and I contacted my internet provide and he gave me instructions on how to possibly fix it but my Network and Sharing center doesn't respond as previously stated by others. What was the outcome ? Did anyone figure out how to fix it ??

stephens316

Dec 12 2007, 11:22 PM

FIXED!

At least for me. I had already taken care of the multimedia issue by reinstalling the Creative Labs SoundBlaster Audigy 2 drivers, but I still had all of the network issues described in this forum. To finally fix the network problems all I did was add the Local Service account to the Administrators group. I'm sure there is some particular file access or registry key access issue that I could have fixed directly and maybe I'll try to find the particular corrupted security setting at a later date. Just in case you need it here are the steps I took...

>>Right click "Computer"
>>Click "Manage"
>>Double click "Users and Groups"
>>Click "Groups"
>>Right click "Administrators"
>>Click "Add to group..."
>>Click "Add"
>>Click "Advanced"
>>Click "Find Now"
>>Double click "Local Service"
>>Click "Ok"
>>"NT Authority\Local Service" should show up in the list now
>>Click "Ok"
>>Close Computer Management and reboot.

Hopefully this will fix it for everyone. If anyone finds the exact file(s) or registry key(s) that needed the permissions modified I'd be interested to know.

You won't in home premium. I found this article http://www.xoxideforums.com/networking/763...you-server.html that says that you can use the command net localgroup "Administrators" "NT Authority\Local Service" /add and that should work. I had to boot my computer up in safe mode with commands to do it but it worked for me. Hope this helps!

BL6ZiNx6iRL

Dec 13 2007, 03:32 AM

QUOTE

Double click "Users and Groups"

Umm ... what do you do if there is no Users and Group catagory ??

stephens316

Dec 13 2007, 11:22 AM

You won't in home premium. you can use the command net localgroup "Administrators" "NT Authority\Local Service" /add and that should work. Boot Your computer up in safe mode with commands to do it. Hope this helps!

I have business ed of vista but i have found this info for you

To all
This is a major security problem in Vista and appears to be related to viewpoint and AIM MS is failing to address it

BL6ZiNx6iRL

Dec 13 2007, 03:04 PM

QUOTE

I have no idea what you just said. I'm not too smart when it comes to computer repairing and stuff. Could you run that by me again in Idi0T mode ??

stephens316

Dec 13 2007, 11:29 PM

1 boot into safe mode with commands do this by hitting F8 key during start up
2log into the system
3start >programs>accessories> command prompt right click Run as Administrator i believe this is a must here
4 should look like C:> or something close type net localgroup "Administrators" "NT Authority\Local Service" /add
5 reboot and see if it fixes it if not

let me know you can reach me on AIM messenger most of the time

BL6ZiNx6iRL

Dec 14 2007, 03:49 AM

Ok, I did the steps you suggested and it didn't work.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.