What is vshare.386? Is vshare.386 spyware or a virus?
How to fix vshare.386 related problems?
1. Run Security Task Manager to check your vshare process
2. Run Windows Repair Tool to repair vshare.386 related Windows Errors
3. Run MalwareBytes to remove persistent malware
Process name: Virtual Share Driver
Product: Microsoft Windows Operating System
Company: Microsoft (microsoft.com)
An old Windows share driver, this file replaced the MS-DOS file share.exe. Vshare.386 ran in enhanced mode and allowed for file sharing across a workgroup, even if Windows was not running. Vshare.386 has not been packaged with Windows installations since Windows 95 was introduced. Founded in 1975, Microsoft's Windows Operating System is on more than 90% of IBM Compatible PCs.
If you want a detailed security rating about your vshare.386 (and all other running background processes) read the following user opinions, and download the free trial version of Security Task Manager.
Note: Any malware can be named anything - so you should check where the files of the running processes are located on your disk. If a "non-Microsoft" .exe file is located in the C:\Windows or C:\Windows\System32 folder, then there is a high risk for a virus, spyware, trojan or worm infection! Check it out!
Average user rating of vshare.386: based on 10 votes. Read also the 7 reviews.
857 users ask for this file. 6 users rated it as not dangerous. 3 users rated it as not so dangerous. One user rated it as neutral. One user didn't rate it ("don't know").
|All comments about vshare.386:|
|From googling I found that some programs don't work with this so I guess it must be normal See also: Link Paul|
|Seems to be windows relatet. See also: Link Lasse F. Sørensen|
|microsoft process See also: Link mushu|
|used to free up conventional memory (instead of "share") according to http://www.empowermentzone.com/w31tips.txt|
|Diese Datei gab es schon bei Windows 3.1 und war der Ersatz für die Datei Share.exe. Nano|
|Per "support.microsoft.com": Many Windows-based applications that support OLE 2.0 require file-sharing and file-locking capabilities to be enabled. This is accomplished by loading VSHARE.386 in the [386Enh] section of the SYSTEM.INI file or by loading SHARE.EXE in the AUTOEXEC.BAT file. See also: Link Henry|
|upper memory manager from old DOS days for dBase 3.0 etc Doug|
More process information
Is vshare.386 spyware or a virus, trojans, adware or worm? Is there a known vshare.386 error?