Whenever i tried to open the file manager it crashes right away but if i go to my Documents for example , i can acess all my files via the dropdown menu like nothing was wrong.

I tried also to right click some folders like c/program files/windowsapp and whenever i right click this folder it crashes too (probably because its a hidden folder and protected[but i got away anyway avoiding to right click and stuff]) Anyone know to fix , i can easily reproduce this error.


Looks like the utx.dll from Autodesk Inventor 2014 cause the crash:

ExceptionAddress: 00007ffd0713a1c8 (KERNELBASE!RaiseException+0x0000000000000068)
   ExceptionCode: e06d7363 (C++ EH exception)
  ExceptionFlags: 00000001
NumberParameters: 4
   Parameter[0]: 0000000019930520
   Parameter[1]: 000000000216abc0
   Parameter[2]: 00007ffcdf76db30
   Parameter[3]: 00007ffcdf600000


PROCESS_NAME:  explorer.exe

ERROR_CODE: (NTSTATUS) 0xe06d7363 - <Unable to get error code text>

EXCEPTION_CODE: (NTSTATUS) 0xe06d7363 - <Unable to get error code text>

EXCEPTION_PARAMETER1:  0000000019930520

EXCEPTION_PARAMETER2:  000000000216abc0

EXCEPTION_PARAMETER3:  00007ffcdf76db30




APP:  explorer.exe


ANALYSIS_VERSION: 10.0.10240.9 amd64fre

LAST_CONTROL_TRANSFER:  from 00000000738814f1 to 00007ffd0713a1c8

00 ntdll!NtWaitForMultipleObjects
01 ntdll!RtlReportExceptionEx
02 ntdll!RtlReportException
03 ntdll!LdrpInitializeNode$filt$1
04 ntdll!_C_specific_handler
05 ntdll!RtlpExecuteHandlerForException
06 ntdll!RtlDispatchException
07 ntdll!RtlRaiseException
08 KERNELBASE!RaiseException
09 msvcr100!CxxThrowException
0a utx
0b utx
0c 0x0
0d utx



FAILURE_ID_HASH_STRING:  um:application_fault_e06d7363_utx.dll!unknown

    Loaded symbol image file: utx.dll
    Image path: C:\Program Files\Autodesk\Inventor 2014\Bin\utx.dll
    Image name: utx.dll
    Browse all global symbols  functions  data
    Timestamp:        Thu Feb 28 22:59:45 2013

Install the latest update and look if this fixes it.

  • Thanks dude ur smart. Invetor 2014 is not compatible with Windows 10, unnistaled and now everything works fine. :D – Rodrigo Aug 5 '15 at 19:37
  • Btw how do i read my dump file as you did? – Rodrigo Aug 5 '15 at 21:05
  • I used Windbg.exe (!analyze -v) from the Windows SDK/Debugger. – magicandre1981 Aug 6 '15 at 4:02
  • hey I tried that but i dont get the same info. i get some symbols error idk do i need anything else installed? 1drv.ms/1P7yKYP – Rodrigo Aug 6 '15 at 4:10
  • you get the same like I did. For the stack command I used kc to remove the parameters. – magicandre1981 Aug 6 '15 at 4:16

Just as an update to the next person coming across this page, I had the exact same problem after KB3081449. Getting rid of it fixed the problem.

  • Thanks, uninstalled KB3081449 and now right click is working again! – TouchBoarder Sep 17 '15 at 10:34

You'll have to delete two updates: KB3081449 (as suggested in Burak's answer) and KB3081448.

To delete this, follow:

  • Settings > Windows Update > Advanced Options > View Your Update History > Uninstall Updates.
  • Choose update, uninstall, restart.

Found this solution in a youtube comment, this worked for me.

Problems started yesterday when I changed the display size from the default setting (150%) to the maximum (175%). You mentioned reverting back to 150%, and bang! problem fixed!

  • Holy crap. This works... Insane. – Guido Bouman Jan 25 '16 at 21:23
  • Yeah, thought the same, a combination of your comments, Fu**ing holy crazy crap. – Viktor Mellgren Jan 26 '16 at 8:44
  • Seriously - could this be a fix? One of my clients has this problem so I rebuilt her PC. Same problem. But the first thing she did was change the display size... currently we've turned recent items off! – munrobasher Aug 25 '16 at 14:57

Explorer crash with right click on everything: To fix it, open Explorer and for every disk partion, select properties (from the ribbon so not crashing) and in security give full control for the user account. Apply and click ok. The problem is resolved.


If you really want to find the cause of explorer crashing, your best bet is to use WinDbg using the steps that Andrew has written here.

Not the answer you're looking for? Browse other questions tagged or ask your own question.