
To stop the creation of the user mode dump files run the following registry file:

Here's a couple of links on using OneDrive (SkyDrive): dmp file available (provide link) via a public folder on OneDrive (SkyDrive) or similar site? dmp file at the time explorer.exeĬrashes should be created in the C:\CrashDumps folder: Windows Registry Editor Version 5.00 reg file and select "Merge" to add to the registry, a. reg extension and give it any name such as dump.reg), then right-click the. If you copy and paste the following in Notepad and save as a. You can configure Windows to create user-mode dumps. see if that lists Explorer crashes, and see what clues that give to an Explorer crash.īeyond that (this info from auggy taken from I'm not sure if this affects what's happening as they didn't have these issues when running Windows7圆4. Drive P is mapped as \\server\Projects instead of \\server\Data\Projects. Within Share2 (Data) is Share1 (Projects).

For example, Server has Share1 (Projects)Īnd Share2 (Data). We noticed this at the end of looking into this again and haven't had a chance to further test, but the one share they primarily access is nested within another share and their mapped drive is pointed at this. Users primarily use AutoCAD software and can't set mapped network paths to their Quick Access toolbar. As a workaround, users can use the network path to access and/or search for files (i.e., \\server\share\AutoCad2016\.) without any issues. Removed this for a few users for testing and manually mapped the drives but still had the issue. The mapped drives are typically done via a logon script in AD. This only seems to be happening when accessing the files via mapped network drives.


This is only happening on clients that have been updated to Windows 10 Anniversary Edition. Things we've noticed so far with some further testing: Happened on our profile as well as the users. Regin - I got the same results when testing this after a clean boot. There's also no virtualization in their environment. The users that are experiencing this thus far don't get any sort of message, just file explorer crashing. Susan - The environment consists of 3 physical servers, all running Server 2008 R2.
