Windows 8 crashes when trying to connect to a Remote Desktop or a VPN
Hello, 

When trying to perform a connection to a remote desktop or a VPN the application crashes (either MSTSC.exe or Explorer.exe). I've noticed this happens when credentials are about to be asked (same happens when trying to access a restricted folder on a network machine).

Useful PC specs:

- i7 3770k, 16GB Ram, GTX460 (2x-SLI) (Intel HD 4000 on board) > All latest drivers and Windows updates installed.

> Ran Memory Diagnostic. No errors.

Event Log:

------------------------------------------------------------------------------- Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1 Faulting module name: DUI70.dll, version: 6.2.9200.16384, time stamp: 0x50108e6a Exception code: 0xc0000005 Fault offset: 0x00000000000027ee Faulting process ID: 0x994 Faulting application start time: 0x01cdf16f9b46e882 Faulting application path: C:\WINDOWS\system32\mstsc.exe Faulting module path: C:\WINDOWS\system32\DUI70.dll Report ID: dadcc27c-5d62-11e2-bf13-bc5ff4390e7a Faulting package full name:  Faulting package-relative application ID:  ------------------------------------------------------------------------------- WinDbg: (RDP Crash dump with procdump) ------------------------------------------------------------------------------- Loading unloaded module list ...... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (994.1118): Access violation - code c0000005 (first/second chance not available) dui70!DirectUI::Element::_SetValue+0xe: 000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=???????????????? 0:000> .ecxr rax=000007fec5cbbd80 rbx=000000989f3afa28 rcx=0000000000000000 rdx=000007fec5cbbd80 rsi=00000000fffffffd rdi=00000098a3e805b0 rip=000007fec5be27ee rsp=000000989f23a8b0 rbp=0000000000000000  r8=0000000000000001  r9=000000989f3afa28 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=00000098a1d29401 iopl=0         nv up ei pl nz na pe nc cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010200 dui70!DirectUI::Element::_SetValue+0xe: 000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=???????????????? 0:000> !analyze -v ******************************************************************************* *                                                                             * *                        Exception Analysis                                   * *                                                                             * ******************************************************************************* GetPageUrlData failed, server returned HTTP status 404 URL requested: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1 FAULTING_IP:  dui70!DirectUI::Element::_SetValue+e 000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx] EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 000007fec5be27ee (dui70!DirectUI::Element::_SetValue+0x000000000000000e)    ExceptionCode: c0000005 (Access violation)   ExceptionFlags: 00000000 NumberParameters: 2    Parameter[0]: 0000000000000000    Parameter[1]: 0000000000000000 Attempt to read from address 0000000000000000 DEFAULT_BUCKET_ID:  NULL_POINTER_READ PROCESS_NAME:  mstsc.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1:  0000000000000000 EXCEPTION_PARAMETER2:  0000000000000000 READ_ADDRESS:  0000000000000000  FOLLOWUP_IP:  dui70!DirectUI::Element::_SetValue+e 000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx] MOD_LIST: <ANALYSIS/> NTGLOBALFLAG:  0 APPLICATION_VERIFIER_FLAGS:  0 FAULTING_THREAD:  0000000000001118 PRIMARY_PROBLEM_CLASS:  NULL_POINTER_READ BUGCHECK_STR:  APPLICATION_FAULT_NULL_POINTER_READ LAST_CONTROL_TRANSFER:  from 000007fec5be7db8 to 000007fec5be27ee STACK_TEXT:   00000098`9f23a8b0 000007fe`c5be7db8 : 00000098`9f23a950 00000098`00000004 00000098`9f23a954 00000098`9f3afa28 : dui70!DirectUI::Element::_SetValue+0xe 00000098`9f23a930 000007fe`b5378a73 : 00000098`a3f11208 00000098`9f23aa70 000007fe`b5418c58 000007fe`c4dc20f5 : dui70!DirectUI::Element::SetLayoutPos+0x98 00000098`9f23a970 000007fe`b53a5f7e : 00000098`a3f154d0 000007fe`b533bd54 00000098`a3ea80e0 00000000`00000000 : authui!UserList::_OnEnumerationSyncReply+0x689 00000098`9f23af80 000007fe`b5332670 : 00000098`a3f111f0 000007fe`b53212d1 00000098`a3f153a0 00000000`00000001 : authui!CCredDialog::UIJobEvent+0x15e 00000098`9f23afc0 000007fe`b533cf1b : 00000000`00000000 00000000`00000000 00000000`00000000 000007fe`cae3545f : authui!CEnumerationSyncReplyJob::DeferredExecute+0x20 00000098`9f23b000 000007fe`b533cfbc : 00000098`a3f111f0 00000000`00000001 00000000`00000000 00000098`0000029e : authui!CDeferredUIThreadJob::Do+0x37 00000098`9f23b030 000007fe`b53a7f42 : 00000098`a1d29350 00000000`000e0602 00000000`00000002 00000000`000e0602 : authui!CCredentialJobQueue::_ProcessJobs+0x69 00000098`9f23b070 000007fe`b53a7e76 : 00000000`00000000 00000000`00000000 00000000`00008003 00000000`00000000 : authui!CCredDialog::DialogProc+0xa2 00000098`9f23b0d0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23b241 00000000`00008003 00000000`00000000 : authui!CCredDialog::s_DialogProc+0x66 00000098`9f23b100 000007fe`c86ab108 : 00000098`9f9522d0 00000000`00000000 00000000`00008003 00000000`00000000 : user32!UserCallDlgProcCheckWow+0x135 00000098`9f23b1d0 000007fe`c86ab02e : 00000000`00000000 00000000`000e0602 00000000`00008003 000007fe`c4dc120b : user32!DefDlgProcWorker+0xb8 00000098`9f23b2a0 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : user32!DefDlgProcW+0x56 00000098`9f23b2e0 000007fe`c86914d7 : 00000098`9f9522d0 00000098`9f23b4e0 000007f7`f30de800 000007fe`cae31b95 : user32!UserCallWinProcCheckWow+0x13a 00000098`9f23b3a0 000007fe`c86be067 : 00000098`9f9522d0 00000098`9f9522d0 00000098`9f9522d0 00000000`00000001 : user32!DispatchMessageWorker+0x1a7 00000098`9f23b420 000007fe`c86bc641 : 00000098`9f9522d0 00000098`9f9522d0 00000000`00000000 00000000`0000c000 : user32!IsDialogMessageW+0x242 00000098`9f23b4b0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007fe`b53a7e10 00000098`9f3a6cd0 : user32!DialogBox2+0xfc 00000098`9f23b540 000007fe`c86bb936 : 000007fe`b5320000 00000000`000909fc 000007fe`b53a7e10 000007fe`b53a7df8 : user32!InternalDialogBox+0x113 00000098`9f23b5a0 000007fe`c86bbc1b : 00000000`00000000 000007fe`b5320000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamAorW+0x56 00000098`9f23b5e0 000007fe`b53a7c91 : 00000000`00000000 00000000`00000000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamW+0x1b 00000098`9f23b620 000007fe`b539d0d0 : 00000098`a1d29350 00000000`00000000 00000098`9f3ec310 000007fe`b7d77987 : authui!CCredDialog::Dialog+0x151 00000098`9f23b670 000007fe`b7d6d268 : 10458c33`00000029 00000098`9f23b800 00000098`9f3ebac0 000007fe`b7d6d370 : authui!CCredUI::CredUIPromptForWindowsCredentialsW+0x1dc 00000098`9f23b700 000007fe`b7d6d503 : 00000098`00000003 00000000`00000000 00000098`9f23ba10 00000098`9f3ebac0 : credui!CredUIPromptForWindowsCredentialsWorker+0x310 00000098`9f23b850 000007fe`ac10c4fd : 00000098`9f3ebac0 00000098`9f23baa0 00000098`9f23ba10 00000098`9f23ba28 : credui!CredUIPromptForWindowsCredentialsW+0x17b 00000098`9f23b8f0 000007fe`ac0a0a85 : 00000000`00000000 00000098`00000000 00000000`00000000 00000000`00000000 : mstscax!CTscCredentialsQueryUi::PromptForCredentialsNew+0x159 00000098`9f23b9c0 000007fe`ac09e8e8 : 00000098`9f362f38 00000000`00000000 00000000`00000000 00000098`a0fed860 : mstscax!CTscCredsAssistant::PromptForTsCredentials+0x4e5 00000098`9f23d050 000007fe`ac0a13f7 : 00000098`9f351050 00000000`00000000 00000000`00000000 00000098`a0f24d50 : mstscax!CTscCredsAssistant::AcquireTsCredentials+0x8f4 00000098`9f23d770 000007fe`ac0716fb : 00000098`a0f24d50 00000098`a0f24d50 00000000`00000000 00000000`00000000 : mstscax!CTscCredsAssistant::OnSecurityLayerNegotiationComplete+0x1af 00000098`9f23e000 000007fe`ac179428 : 00000098`00000002 00000098`a0f5fee0 00000098`a0f5fee0 00000000`00000001 : mstscax!CUI::OnSecurityLayerNegotiationComplete+0x11f 00000098`9f23e060 000007fe`ac179594 : 00000098`a0f1c540 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::RunQueueEvent+0x104 00000098`9f23e0b0 000007fe`ac17baf2 : 00000098`a0f1c540 000007fe`c8691742 00000098`a0f1bf30 00000000`00000000 : mstscax!CTSThread::RunAllQueueEvents+0xcc 00000098`9f23e110 000007fe`ac17bb28 : 00000098`a0f1bf30 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::OnNotifyThreadEventQueue+0xa6 00000098`9f23e150 000007fe`abefb451 : 00000000`00000000 00000000`00000000 000061f5`6df98991 ffffffff`ffffffff : mstscax!CTSThread::OnNotifyThreadMessage+0x20 00000098`9f23e180 000007fe`c869171e : 000007fe`c8691742 00000000`00000000 00000000`00035090 00000098`9f919f70 : mstscax!PAL_System_Win32_ThreadWndProc+0x19 00000098`9f23e1b0 000007fe`c86914d7 : 00000098`9f94fb70 00000098`9f23e320 000007f7`f30de800 000007fe`abefb438 : user32!UserCallWinProcCheckWow+0x13a 00000098`9f23e270 000007fe`c86bc6c4 : 00000098`9f950eb0 00000098`9f950eb0 00000000`00000001 00000000`0000c000 : user32!DispatchMessageWorker+0x1a7 00000098`9f23e2f0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007f7`f331d518 000007fe`c81931b2 : user32!DialogBox2+0x219 00000098`9f23e380 000007fe`c86bb936 : 000007f7`f32c0000 00000000`000909fc 000007f7`f331d518 00000000`000909fc : user32!InternalDialogBox+0x113 00000098`9f23e3e0 000007fe`c86bbbe9 : 000007f7`f32c0000 00000098`9f23e4e0 00000000`000909fc 00000000`00000000 : user32!DialogBoxIndirectParamAorW+0x56 00000098`9f23e420 000007f7`f331d788 : 00000000`000909fc 00000098`9f23e570 00000098`9f23e4e0 ffffffff`ffffffff : user32!DialogBoxParamW+0x69 00000098`9f23e460 000007f7`f331ce9e : 00000098`a0efedc0 000007f7`f32c7ab0 000007f7`f333b420 00000000`00000000 : mstsc!CDlgBase::CreateModalDialog+0x168 00000098`9f23e500 000007f7`f32e2604 : 00000098`a0efedc0 00000098`9f23ead0 000007f7`f32c7ab0 00000000`00000000 : mstsc!CDlgBase::DoModal+0x12 00000098`9f23e540 000007f7`f32dbd6b : 00000098`9f4ec3e0 00000098`9f4ec3e0 000007f7`f32c7ab0 000007f7`f333b420 : mstsc!CDefaultContWndExt::OnConnectionIssued+0xec 00000098`9f23e9d0 000007f7`f3302bd9 : 000007f7`f32cbb00 000007f7`f32cbb00 00000000`00000000 00000098`a0f1f350 : mstsc!CContainerWnd::StartConnection+0x4d7 00000098`9f23ee70 000007f7`f3301feb : 00000000`000909fc 00000000`00000111 00000000`000c09be 00000000`00000001 : mstsc!CMainDlg::DialogBoxProc+0xbb9 00000098`9f23f1b0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23f331 00000000`00000111 00000000`00000000 : mstsc!CMainDlg::StaticDialogBoxProc+0x63 00000098`9f23f1f0 000007fe`c86ab108 : 00000098`9f919f70 00000000`00000000 00000000`00000111 00000000`00000001 : user32!UserCallDlgProcCheckWow+0x135 00000098`9f23f2c0 000007fe`c86ab02e : 00000000`000c09be 00000098`9f23f500 00000000`00000111 000007fe`cae31b95 : user32!DefDlgProcWorker+0xb8 00000098`9f23f390 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 000007fe`c8be1535 : user32!DefDlgProcW+0x56 00000098`9f23f3d0 000007fe`c86d22f9 : 00000000`000c09be 00000000`00000111 00000000`80000000 00000000`00000000 : user32!UserCallWinProcCheckWow+0x13a 00000098`9f23f490 000007fe`c869487a : 00000000`00000000 00000000`00000000 00000000`00000001 00000098`9f919f70 : user32!SendMessageWorker+0xa72 00000098`9f23f540 000007fe`c86bbdd3 : 00000000`00090a12 00000098`9f919f70 00000000`000909fc 00000000`000909fc : user32!SendMessageW+0x10a 00000098`9f23f5a0 000007f7`f3312409 : 00000098`a0ef0080 00000098`a0ef0080 00000000`00000000 00000000`03260475 : user32!IsDialogMessageW+0x40b 00000098`9f23f630 000007f7`f3312a07 : 000007f7`f32c0000 00000098`9f312374 000007f7`f333b420 000007f7`00000000 : mstsc!TSCMain+0x695 00000098`9f23f6e0 000007f7`f33319c9 : 00000098`9f313100 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!WinMain+0x42f 00000098`9f23f750 000007fe`c8fe167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!ATL::AtlWinModuleTerm+0x375 00000098`9f23f810 000007fe`cae53501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a 00000098`9f23f840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d STACK_COMMAND:  ~0s; .ecxr ; kb SYMBOL_STACK_INDEX:  0 SYMBOL_NAME:  dui70!DirectUI::Element::_SetValue+e FOLLOWUP_NAME:  MachineOwner MODULE_NAME: dui70 IMAGE_NAME:  dui70.dll DEBUG_FLR_IMAGE_TIMESTAMP:  50108e6a FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_dui70.dll!DirectUI::Element::_SetValue BUCKET_ID:  X64_APPLICATION_FAULT_NULL_POINTER_READ_dui70!DirectUI::Element::_SetValue+e WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1 Followup: MachineOwner ------------------------------------------------------------------------------- Any ideas what could be the problem and how to resolve this?
January 18th, 2013 12:39am

Try to boot in Clean Boot Mode to troubleshoot.

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

Free Windows Admin Tool Kit Click here and download it now
January 21st, 2013 10:45am

Since this is access violation in Direct UI module, what if you

  • Run sfc /scannow to validate consistency of Windows modules.
  • Remove and install again your NVidia's driver?
January 21st, 2013 2:09pm

Exotic Hadron, sfc /scannow I already tried that, I should have mentioned it in my initial post. It didn't help... As for the drivers, also tried that (even tried rolling back to previous versions and updating the Intel HD 4000 on board card's drivers), no success.

Arthur Xie, Clean boot mode did not seem to make a difference.

Free Windows Admin Tool Kit Click here and download it now
January 21st, 2013 8:12pm

Do you by chance have Intel adapter enabled in BIOS? I don't think that's the problem, but what if you completely disable it since you are using discrete VGA adapter from NVidia?
January 21st, 2013 8:19pm

Hadron, unfortunately disabling the onboard intel gfx does not help resolve the problem either. I also tried running only on the intel graphics to no avail.

It's very strange, as you said a sfc /scannow command should fix any system related issues for these modules, now I wonder if a clean install is the only solution to this, but one I'd rather avoid of course.

Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2013 8:51am

Further proof it's something with credentials/authentication. I found a valid workaround, but I think this one's on Microsoft to actually fix.

I opened up Remote Desktop Connection, put in my username and clicked the Save Credentials box. Then I edited all the other settings. Saved the RDP connection to my desktop. Then I edited it with notepad, and added the password value. I found a blog that provides a program that'll hash the password for you. I used it so I can say its safe:

http://www.remkoweijnen.nl/blog/2007/10/18/how-rdp-passwords-are-encrypted/

I put the hashed password in, saved the file. Then used it to connect and it worked. So by bypassing RDP having to ask for credentials, it didn't crash since it doesn't ask. Kind of inconvenient if you have many computers you have to connect in to. But for those in a bind this will work for you.


  • Edited by cdegaeta920 Saturday, June 01, 2013 8:28 PM
  • Proposed as answer by ThinSTAR Saturday, August 03, 2013 11:54 AM
June 1st, 2013 7:17pm

Have you ever found a conclusion to this? I basically have the exact same dmp results, and can confirm this happens when Remote Desktop asks for credentials. Putting in saved credentials does not make a difference. This occurs when connecting to computers that are Vista or better. Attempting to connect to any Windows computer that is XP or 2003 works just fine.

Seems to be an issue with the latest version of RDP client. It's pretty much driving me nuts because I have another Windows 8 computer that does not have this problem. Same updates but not same hardware. But the dmp file doesn't mention any hardware drivers to be the issue. Just files dealing with logging in and credentials.

Free Windows Admin Tool Kit Click here and download it now
June 1st, 2013 8:19pm

Further proof it's something with credentials/authentication. I found a valid workaround, but I think this one's on Microsoft to actually fix.

I opened up Remote Desktop Connection, put in my username and clicked the Save Credentials box. Then I edited all the other settings. Saved the RDP connection to my desktop. Then I edited it with notepad, and added the password value. I found a blog that provides a program that'll hash the password for you. I used it so I can say its safe:

http://www.remkoweijnen.nl/blog/2007/10/18/how-rdp-passwords-are-encrypted/

I put the hashed password in, saved the file. Then used it to connect and it worked. So by bypassing RDP having to ask for credentials, it didn't crash since it doesn't ask. Kind of inconvenient if you have many computers you have to connect in to. But for those in a bind this will work for you.


June 1st, 2013 10:17pm

Further proof it's something with credentials/authentication. I found a valid workaround, but I think this one's on Microsoft to actually fix.

I opened up Remote Desktop Connection, put in my username and clicked the Save Credentials box. Then I edited all the other settings. Saved the RDP connection to my desktop. Then I edited it with notepad, and added the password value. I found a blog that provides a program that'll hash the password for you. I used it so I can say its safe:

http://www.remkoweijnen.nl/blog/2007/10/18/how-rdp-passwords-are-encrypted/

I put the hashed password in, saved the file. Then used it to connect and it worked. So by bypassing RDP having to ask for credentials, it didn't crash since it doesn't ask. Kind of inconvenient if you have many computers you have to connect in to. But for those in a bind this will work for you.


  • Edited by cdegaeta920 Saturday, June 01, 2013 8:28 PM
  • Proposed as answer by KildalK Saturday, August 03, 2013 11:54 AM
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2013 10:17pm

Thanks for contributing cdegaeta920. No, nothing I did seemed to fix the error. At the end I did a fresh windows 8 installation (had some other issues as well), and the behavior did not appear again. It seems some update or something in the initial installation caused the credentials screen to crash the explorer, still don't know what though.
July 11th, 2013 11:45am

Thanks for contributing cdegaeta920. No, nothing I did seemed to fix the error. At the end I did a fresh windows 8 installation (had some other issues as well), and the behavior did not appear again. It seems some update or something in the initial installation caused the credentials screen to crash the explorer, still don't know what though.
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2013 3:43pm

Thanks for contributing cdegaeta920. No, nothing I did seemed to fix the error. At the end I did a fresh windows 8 installation (had some other issues as well), and the behavior did not appear again. It seems some update or something in the initial installation caused the credentials screen to crash the explorer, still don't know what though.
July 11th, 2013 6:43pm

Further proof it's something with credentials/authentication. I found a valid workaround, but I think this one's on Microsoft to actually fix.

I opened up Remote Desktop Connection, put in my username and clicked the Save Credentials box. Then I edited all the other settings. Saved the RDP connection to my desktop. Then I edited it with notepad, and added the password value. I found a blog that provides a program that'll hash the password for you. I used it so I can say its safe:

http://www.remkoweijnen.nl/blog/2007/10/18/how-rdp-passwords-are-encrypted/

I put the hashed password in, saved the file. Then used it to connect and it worked. So by bypassing RDP having to ask for credentials, it didn't crash since it doesn't ask. Kind of inconvenient if you have many computers you have to connect in to. But for those in a bind this will work for you.


This one worked for me, no update or installation of software before it broke, but had a "wife-poweroutage" (cable taken out) I'm just not in the mood to reinstall for this. But the above fixed it for me. Thank you!

Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2013 8:04am

Hi, i've the same trouble.

Any program that use the microsoft's credential request window, hangs.

I found the solution in a registry key that I had change:

HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\UserSwitch

Name: Enabled (DWORD)

Default Value: 0

I changed it to 1 in order to remove autologon.

Put back into 0 and problem solved

  • Proposed as answer by Duncan Smart Wednesday, October 30, 2013 9:19 AM
September 20th, 2013 8:01pm

Hi, i've the same trouble.

Any program that use the microsoft's credential request window, hangs.

I found the solution in a registry key that I had change:

HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\UserSwitch

Name: Enabled (DWORD)

Default Value: 0

I changed it to 1 in order to remove autologon.

Put back into 0 and problem solved

  • Proposed as answer by Duncan Smart Wednesday, October 30, 2013 9:19 AM
Free Windows Admin Tool Kit Click here and download it now
September 20th, 2013 11:01pm

Thanks @moretti84 this was exactly what I'd done (http://winaero.com/blog/how-to-disable-automatic-logon-of-last-user-in-window-8/)
October 30th, 2013 12:22pm

I could log onto a 2003 server fine, but couldn't log remotely onto my Win 7 PC.  It crashed at the credentials.  I had the same error in the Windows log (1000) for DUI70.dll.

I don't know what update or install changed this reg key, but switching the value back to 0 stopped the crashing and let me authenticate.

Thanks for the find!!!

Free Windows Admin Tool Kit Click here and download it now
January 14th, 2014 9:26pm

Same here, changed the UserSwitch long time ago. Won 8.1 RDP also crash when this registry key is set to 1. Back to 0 and RDP works again like a charm.

Thx moretti84

July 10th, 2015 12:52pm

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

Other recent topics Other recent topics