{5eeb83d0-96ea-4249-942c-beead6847053}w64.sys is part of StdLib and developed by StdLib according to the {5eeb83d0-96ea-4249-942c-beead6847053}w64.sys version information.
{5eeb83d0-96ea-4249-942c-beead6847053}w64.sys's description is "StdLib"
{5eeb83d0-96ea-4249-942c-beead6847053}w64.sys is digitally signed by SmarterPower.
{5eeb83d0-96ea-4249-942c-beead6847053}w64.sys is usually located in the 'C:\Windows\system32\drivers\' folder.
Some of the anti-virus scanners at VirusTotal detected {5eeb83d0-96ea-4249-942c-beead6847053}w64.sys.
If you have additional information about the file, please share it with the FreeFixer users by posting a comment at the bottom of this page.
The following is the available information on {5eeb83d0-96ea-4249-942c-beead6847053}w64.sys:
| Property | Value |
|---|---|
| Product name | StdLib |
| Company name | StdLib |
| File description | StdLib |
| Internal name | StdLib.sys |
| Original filename | StdLib.sys |
| Legal copyright | Copyright © 2013 StdLib |
| Product version | 1.4.3.1 |
| File version | 1.4.3.1 built by: WinDDK |
Here's a screenshot of the file properties when displayed by Windows Explorer:
| Product name | StdLib |
| Company name | StdLib |
| File description | StdLib |
| Internal name | StdLib.sys |
| Original filename | StdLib.sys |
| Legal copyright | Copyright © 2013 StdLib |
| Product version | 1.4.3.1 |
| File version | 1.4.3.1 built by: WinDDK |
{5eeb83d0-96ea-4249-942c-beead6847053}w64.sys has a valid digital signature.
| Property | Value |
|---|---|
| Signer name | SmarterPower |
| Certificate issuer name | VeriSign Class 3 Code Signing 2010 CA |
| Certificate serial number | 38d7c83a73cb4e3ac85648608e3170d8 |
12 of the 55 anti-virus programs at VirusTotal detected the {5eeb83d0-96ea-4249-942c-beead6847053}w64.sys file. That's a 22% detection rate.
| Scanner | Detection Name |
|---|---|
| Agnitum | PUA.Yotoon! |
| AhnLab-V3 | Trojan/Win64.SwiftBrowse |
| AVG | Generic.E07 |
| AVware | Trojan.Win32.Generic!BT |
| DrWeb | Trojan.BPlug.123 |
| Ikarus | AdWare.SwiftBrowse |
| Jiangmin | AdWare/Yotoon.m |
| McAfee | Artemis!05B0BFE5D4D0 |
| McAfee-GW-Edition | Artemis!05B0BFE5D4D0 |
| TrendMicro-HouseCall | Suspicious_GEN.F47V0822 |
| VIPRE | Trojan.Win32.Generic!BT |
| Zillya | Adware.Yotoon.Win64.3 |
The instructions below shows how to remove {5eeb83d0-96ea-4249-942c-beead6847053}w64.sys with help from the FreeFixer removal tool. Basically, you install FreeFixer, scan your computer, check the {5eeb83d0-96ea-4249-942c-beead6847053}w64.sys file for removal, restart your computer and scan it again to verify that {5eeb83d0-96ea-4249-942c-beead6847053}w64.sys has been successfully removed. Here are the removal instructions in more detail:
| Property | Value |
|---|---|
| MD5 | 05b0bfe5d4d0575e6352e5e94a0c4588 |
| SHA256 | e1befa104b2beea013aeca256b5dd571691bec7a6c22117b132d62f30f4f39c6 |
To help other users, please let us know what you will do with the file:
Please share with the other users what you think about this file. What does this file do? Is it legitimate or something that your computer is better without? Do you know how it was installed on your system? Did you install it yourself or did it come bundled with some other software? Is it running smoothly or do you get some error message? Any information that will help to document this file is welcome. Thank you for your contributions.
I'm reading all new comments so don't hesitate to post a question about the file. If I don't have the answer perhaps another user can help you.
"{5eeb83d0-96ea-4249-942c-beead6847053}w64"
This is the file discovered by an AVG tune-up scan which is identified as a device not working properly, and states
"This can have the following consequences:
The device may be unusable
The computer may crash often
The computer may go a long time without responding
Computer performance may be very poor", all of which are very true!!
Following the instructions to go in to Device Manager,I located the file and under 'Driver' current status it is stopped, and will not start as the system cannot apparently find the file. I haven't a clue where it came from but it appears that the AVG tune-up tool regards it as a positive file, and I don't know now whether I should use freefixer and delete it or try to re-install it. I would be most grateful for any advice. Many thanks, Ian
# 12 Jul 2015, 6:00
Ian Jordan writes