Eligibility: McAfee® Identity Monitoring.See System Requirements for additional information. Subscriptions covering "all" devicesĭevices. Your subscription is subject to our License Agreement and Privacy Notice.You may request a refund by contacting Customer Support within 30 days of initial purchase or.Time after purchase from your My Account page. The amount you are charged upon purchase.Look there for any evidence of incoming activity from Microsoft servers. 'Threats Detected' should mostly be cookies 'Incoming Events' will have a lot of unsuccessful port access attempts (you don't see the ones which succeeded). If you want to see what's been going on, to check whether you might have been probed by a hacker (or just contacted by Microsoft with an update) you can look in the various logs in the Security Center : click on Navigation/History and Logs and then just run through the various headings looking for anything untoward. Task Manager won't give you that information, but Process Explorer will. Experience will help you to decide.Įxplorer.exe is a safe application provided that what is running is located in the c:\windows directory and is signed by Microsoft. If a program has unrestricted access then you'll never know when it's sending or receiving data : which is okay for some trusted programs but not others. You'll just get more pop-ups asking you to confirm whether to allow access (as long as you've set the Firewall's 'Enable SmartAdvice' and set it to 'Ask me to decide' rather than 'Decide Automatically'. Some do others can get by with restricted access. So I killed the explorer.exe process on the user’s machine and browsed to C:\Users\\AppData\Local\Microsoft\Windows\Explorer and deleted the thumbnails cache files which are located there.McAfee's own advice is that relatively few programs need full access to the internet to be allowed in the firewall (see the online help section here). In this particular crash, we could instantly determine that the cause was thumbcache.dll.Īs the problem was related to thumbnails cache, the first thing to try I thought was deleting the thumbnails cache. To get all the details about the crash you have to type: The necessary symbol files will now be downloaded from Microsoft. Before doing this copy the file to the machine where you will analyze this.īrowse to the location of the DMP file and choose to load it and if you get a question if you want to save the workspace you choose Yes. This is the file that contains the key to the crash and to analyze it first open it by going to Open and then choosing Open Crash Dump. When the process crashes a snapshot of the memory is dumped to a file on the user’s computer. Now type a path to a directory on the hard drive, for example: To set this up, in WinDbg, go to Open and choose Symbol file path. These can be downloaded as one package but it is much more convenient to setup Windows Debugging Tools to download files as necessary. To be able to get a result from the debugging of the DMP file and find the cause of the problem you will need the symbol files. To analyze the problem we will be working with the Microsoft tool Windows Debugging Tools which can be downloaded for free from Microsoft (part of the Windows SDK), (look for Get debugging Tools).Īfter installing Windows Debugging Tools, start it from the Start menu, it is called WinDbg (x86) or WinDbg (圆4). Now reproduce the problem so that a crash dump is generated! HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps On the machine which have the problem, start by activating the creation of crash dump files to get the information you need by setting the following registry values: Report ID: cf2ee514-f280-4942-8225-4c7fb440f27b InvestigationĪs the problem above does not really tell us anything useful we need to obtain more information on the problem. In the Application log in Event Viewer the following event was logged:įaulting application name: Explorer.EXE, version 3.479, time stamp 0x58258a90įaulting module name: ntdll.dll, version 3.479, time stamp 0x5825887fįaulting application start time: 0x01d290d349d6a062įaulting application path: C:\WINDOWS\Explorer.EXEįaulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Every time the user tried to open Windows File Explorer, it crashed, restarting the entire EXPLORER.EXE process. ProblemĪ user experienced a problem after upgrading Windows 10 version 1511 to 1607. This guide can be used as inspiration for troubleshooting similar problems or for use with any application or process that crashes. This is a schoolbook example of how to solve an annoying EXPLORER.EXE crash problem in just minutes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |