What does the iExplorer.exe file do?
The iExplorer.exe process is also known as yasldlyl.exe or, as the case may be, AutoIt v3 Script and is a part of Stub or, as the case may be, wZWXLXCeB. This software is produced by Microsoft (www.microsoft.com) or, as the case may be, AutoIt Team. An obsolete or defective version of iExplorer.exe can cause problems for your computer that can range from slowness to error messages such as these:
- yasldlyl.exe has stopped working. Windows is checking for a solution to the problem... (Windows 10, 8, 7)
- yasldlyl.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. (Windows 10, 8, 7)
- iExplorer.exe has encountered a problem and needs to close. (Windows XP)
- Access violation at address FFFFFFFF in module iExplorer.exe. Read of address 00000000.
Free PC Check
Scan your computer today at no charge with the Windows Repair Tool. This tool helps repair Windows and helps it run faster.
What you should know about iExplorer.exe yasldlyl.exe
iExplorer.exe is not a Windows system file and is known to frequently cause computer problems. The file iExplorer.exe is found in a subdirectory of "C:\Users\USERNAME".
Frequently occurring are file sizes such as 87,040 bytes (10% of all these files), 1,337,344 bytes as well as 8 other variants.
The iExplorer file is not part of the Windows operating system. IExplorer.exe does not supply any version information or other description. The application is initiated as part of Windows start-up (Registry: Run, MACHINE\Run, MACHINE\RunServices, MACHINE\RunServicesOnce, User Shell Folders, NT\Load, DEFAULT\Run). This particular software does not have a visible window, and does not appear on the taskbar. IExplorer.exe is capable of log keyboard entries, Change the behavior of other applications as well as monitor other applications. For this reason, 50% of all experts consider this file to be a possible threat. The probability that it can cause harm is high.
- A iExplorer.exe file has a 79% certainty of being dangerous if it is found in the C:\Windows directory. In this case, the file size is usually 63,488 bytes (28% of all these files), 28,672 bytes as well as 4 other variants. IExplorer.exe has none of the usual file information, such as version number, etc. This iExplorer.exe process is initiated as part of Windows start-up (Registry: Run, MACHINE\Run, MACHINE\RunServices, MACHINE\RunServicesOnce, User Shell Folders, NT\Load, DEFAULT\Run). This file does not come from Microsoft and is not part of the operating system. It is interesting to note that the file is placed in the Windows folder, even though it is not part of the operating system. This iExplorer program does not have a visible window, and does not appear on the taskbar. IExplorer.exe is capable of supervise programs as well as Change the behavior of other applications.
- A iExplorer.exe file has a 66% certainty of being dangerous if it is found in a subdirectory of C:\. In this case, the file size is usually 645,120 bytes (25% of all these files), 32,768 bytes, 644,545 bytes or, as the case may be, 49,152 bytes. This file contains no information about the producer or the version. This process does not appear as a visible window, but only in Task Manager. It was developed by a so-called third party provider - and not by Microsoft. When Windows starts, this process is automatically started at the same time (Registry: Run, MACHINE\Run, MACHINE\RunServices, MACHINE\RunServicesOnce, User Shell Folders, NT\Load, DEFAULT\Run). IExplorer.exe is capable of log keyboard entries.
- A iExplorer.exe file has a 71% certainty of being dangerous if it is found in the C:\Windows\System32 directory. In this case, the file size is usually 20,828 bytes (50% of all these files), 16,702 bytes or, as the case may be, 335,360 bytes.
- A iExplorer.exe file has a 63% certainty of being dangerous if it is found in a subdirectory of "C:\Program Files". In this case, the file size is usually 1,206,552 bytes (33% of all these files), 34,816 bytes or, as the case may be, 387,402 bytes.
- A iExplorer.exe file has a 60% certainty of being dangerous if it is found in the Windows Temp directory. In this case, the file size is usually 152,576 bytes (50% of all these files) or, as the case may be, 2,112 bytes.
- A iExplorer.exe file has a 46% certainty of being dangerous if it is found in a subdirectory of C:\Windows. In this case, the file size is usually 540,672 bytes.
- A iExplorer.exe file has a 56% certainty of being dangerous if it is found in in a subdirectory of the Windows Temp folder. In this case, the file size is usually 323,048 bytes.
If you see this file on your hard drive or in Windows Task Manager, please make sure that it is not a malicious variant. It's a fact that many trojans try to cloak their true identity by calling themselves iExplorer.exe. With the above information or by using tools like Security Task Manager you can determine if, in your case, the file is an undesirable variant.
What do other computer users say about iExplorer?
|hogging all virtual memory on three of my family's computers. It seems to want to share internet providing duties between explorer.exe and itself, iexplorer.exe. I'm not sure why. All I know is that it slows the internet to a crawl. Dial up seems faster than DSL with iexplorer.exe. I ended the process in my virtual memory and it seemed to stop and my connection was back to normal. |
|This one took me awhile to figure out. First of all, the iexplorer I got was a memory hog that slowed down the internet. It immitates the good file, iexplore.exe. I found it and deleted it in the internet explorer folder. After deleting it, windows "healed" that "wound" by replacing it by itself with iexplore.exe. And since then, I haven't had any problems with it. Remember, don't delete iexplore.exe, this is a good file. Delete the malware copy/immitation iexplorer.exe, and, if it works like mine did, windows will replace the missing hole you've created with the real file. |
|Spyware created in C:\windows\iexplorer.exe |
|I had one and ended up to reformat . |
Summary: 6 users judge iExplorer.exe to be an essential file that should not be touched. One user considers it harmless. However, one user considers this to be a suspicious process and would like to get rid of it. For this reason, 8 users have already deleted iExplorer.exe. source: file.net
How to uninstall Stub or wZWXLXCeB
To remove yasldlyl.exe from your computer, please follow the manual instructions below or use an automatic uninstaller product.
- Click the Windows Start Button. In Windows 8, look for Control Panel.
- Click Control Panel.
- Click Uninstall a program.
- Look for Stub or wZWXLXCeB in the list of available programs.
- Click Uninstall.
How to tell if iExplorer.exe (yasldlyl.exe) was uninstalled cleanly
After uninstalling, restart your computer. Then start Windows Explorer and see if there is still a folder with the name of the software under C:\Program Files. Be sure to check the Registry as well for remnants of yasldlyl.exe. To do this, start "Regedit", then look under "HKEY_LOCAL_MACHINE" > "Software" for yasldlyl.exe or the name of the producer. Always keep in mind that only a computer professional should ever directly delete entries in the Windows Registry.
What to do if a program does not uninstall
The easiest way to remove any kind of software cleanly and accurately is to use an uninstaller tool. Because the uninstaller automatically creates a backup, there is no risk of anything going wrong.
Last but not least
If Windows not working quite right for you, or if startup is taking a long time, or iExplorer.exe is causing problems for you, a good Windows diagnostic tool may very well help. This is especially effective when it comes to older computers that have accumulated vast quantities of "garbage data" as the result of many software installs and uninstalls.
Users with an interest in iExplorer.exe have also been interested in: tbmon.exe checkupdate.exe adaptivesleepservice.exe iExplorer.exe ischedulesvc.exe panda_url_filteringb.exe gammatray.exe synciosdeviceservice.exe [index]