.386

Arquivo 386

Windows Virtual Device Driver (VxD)
Fazer uma pergunta
RESPOSTA RÁPIDA

A 386 file is a Windows Virtual Device Driver (VxD), a low-level kernel-mode driver used by Windows 3.x, 95, 98, and Me to manage hardware. Windows loads these files automatically at startup - you cannot open them manually. On Windows XP and later, they do nothing; VxD support was removed entirely.

Desenvolvedor: Microsoft Corporation Categoria: Arquivos de Sistema MIME: application/octet-stream
ABRE EM Windows
Relacionado: .NOMEDIA · .DLL · .TMP · .LNK

Nesta página

19k+ extensões indexadas
Última revisão em Aug 16, 2026

Não tem certeza do que é seu arquivo?

Arraste qualquer arquivo para o nosso identificador - lemos apenas os primeiros bytes para nomear o formato.

Identificar um arquivo

O que é o formato de ficheiro 386?

.386 files are Virtual Device Drivers (VxDs) for Windows 386 Enhanced Mode, introduced with Windows/386 2.x in 1988. A VxD is a kernel-mode binary component that virtualizes a hardware device or OS service - such as a timer, keyboard, display adapter, or disk controller - so that multiple DOS applications running simultaneously can each believe they have exclusive access to the hardware.

Internally, a .386 file is an MZ DOS executable stub followed by a Linear Executable (LE) header. The LE header carries a VxD descriptor block identifying the device ID, version, and entry points for initialization, I/O port virtualization, and interrupt handling. Windows/386 2.x used an earlier proprietary W386 header format before the LE standard was adopted.

.386 VxDs run entirely in Ring 0 (kernel mode) with no memory isolation. This made them powerful but unstable: a faulty driver could crash the entire operating system. Windows NT used the WDM (Windows Driver Model) with proper kernel isolation from the start; Windows 98 SE began the transition, and Windows Me was the last consumer release to support VxDs. Windows XP and later cannot load .386 files at all - the VxD subsystem was removed.

The same virtual device driver role is also filled by .vxd files (functionally identical, different extension used for dynamic VxDs under Windows 95/98). Well-known examples include VSHARE.386, VFAT.386, and VTDAPI.386. These files are loaded automatically by the Windows kernel at boot or on demand; they cannot and should not be opened manually.

Segurança e proteção

RISCO: MEDIUM

Legitimate .386 files are Windows system drivers, harmless on modern Windows (they do not load). However, malware historically used the .386 extension on Windows 9x/Me to disguise kernel-mode payloads - on those OSes, Ring 0 VxDs could hide themselves from antivirus. On Windows XP and later, .386 files cannot load as VxDs and pose no execution risk. If antivirus flags a .386 file on a modern system, it is likely a historical detection signature or a file disguised with the .386 extension.

Detalhes do formato

em resumo
NOME COMPLETOWindows Virtual Device Driver (VxD)também conhecido como VxD, 386 enhanced mode driver
DESENVOLVEDORMicrosoft Corporationdesde 1988 (Windows/386 2.x)
TIPO MIMEapplication/octet-stream
TIPOVirtual Device Driver for Windows 386 Enhanced Mode (binary executable)
Esta extensão também é usada por…
  • Ventura Publisher font file - Some versions of Xerox/Corel Ventura Publisher used .386 for downloadable 386-optimised font data - rare, pre-1995.
MAGIC BYTES · ASSINATURA DO ARQUIVO
OFFSET
0001
HEX
4D5A
ASCII
MZ
.386 VxD files are DOS executables with an MZ stub followed by an LE (Linear Executable) header. The LE header magic is 0x4C 0x45 ("LE"). Within the LE header, offset 0x10 contains flags that distinguish static VxDs (Windows 3.x) from dynamic VxDs (Windows 9x/Me). The earliest Windows/386 2.x VMM used a bespoke "W386" header instead of LE.

Programas que abrem arquivos 386

Windows3 apps
Microsoft Windows (3.x / 95 / 98 / Me - kernel loads automatically) Pago Not user-openable. Windows loads .386 VxDs automatically from SYSTEM.INI [386Enh] section or the \WINDOWS\SYSTEM folder at startup.
HxD Hex Editor (inspect only) Gratuito Open as binary to inspect the LE header and VxD descriptor block. Cannot execute or load the driver.
IDA Pro / Ghidra (reverse engineering) Código aberto Ghidra supports LE (Linear Executable) format for disassembling legacy VxDs.

Detalhes técnicos

especificação profunda
EncodingBinary executable (MZ DOS stub + Linear Executable LE body)
Byte orderLittle-endian
File headerMZ header (4D 5A) at offset 0 (DOS stub); LE header (4C 45) at offset pointed to by dword at 0x3C
Earliest format variantWindows/386 2.x (1988): proprietary W386 header, predating the LE standard
Execution ringRing 0 (kernel mode) - VxDs run with full hardware access and no memory isolation
Typical file size2 KB - 200 KB
VxD descriptor blockIdentifies device ID, version, and entry points: initialization, I/O port handling, interrupt virtualization
OS compatibilityWindows 2.x (Windows/386) through Windows Me; not loadable on Windows XP or later
Successor technologyWDM (Windows Driver Model) introduced in Windows 98 SE / Windows 2000; drivers use .sys extension
Dynamic loadingSupported from Windows for Workgroups 3.11 onward; earlier versions used static VxDs only
Notable examplesVSHARE.386, VFAT.386, VTDAPI.386, EMM386.386, WINA20.386
Lançado1988 (Windows/386 2.x)
Versão mais recenteUsed through Windows Me (2000); superseded by WDM in Windows 98 SE / 2000
Especificaçãodevblogs.microsoft.com

Conversões de 386

Perguntas e Respostas da Comunidade

perguntado por usuários
Faça uma pergunta rápida
Obtenha ajuda de pessoas que trabalham com arquivos 386. Seja específico - inclua seu sistema e a versão do software.
Não é necessário criar conta · respostas geralmente em um dia

Ainda não há perguntas - seja o primeiro a perguntar sobre arquivos 386.

Perguntas frequentes

What is a .386 file?
A Virtual Device Driver (VxD) used by Windows 3.x, 95, 98, and Me to manage hardware. Not a user document - Windows loads it automatically as a system component.
Can I open a .386 file on Windows 10 or 11?
Not as a driver - Windows XP removed VxD support. You can inspect the binary contents with a hex editor or disassemble it with Ghidra, but it serves no function on modern Windows.
Is a .386 file dangerous?
On modern Windows (XP+), no - VxDs cannot load. On Windows 95/98/Me (historical), a malicious .386 VxD was a serious threat because it ran in kernel mode (Ring 0). Antivirus may still flag old .386 files based on historical signatures.
Should I delete .386 files I find?
If they are in a legacy Windows 3.x/9x installation archive, keep them. If they appear unexpectedly on a modern system, they are inert but worth checking with antivirus for historical malware signatures.
What replaced the .386 VxD format?
WDM (Windows Driver Model) introduced in Windows 98 SE / Windows 2000, using .sys files in PE format. This model is still used today (Windows 10/11).

Referências

1Wikipedia - VxD (Virtual Device Driver)en.wikipedia.org
2Raymond Chen (MS) - The story of WINA20.386devblogs.microsoft.com

Continue explorando

em todo o banco de dados

Principais extensões desta semana

1.AQQAQQ Instant Messenger File
2.CRDOWNLOADChrome Partial Download File
3.PARTPartial Download File
4.EXEWindows Executable (Portable Executable)
5.M4AMPEG-4 Audio File
6.DATProgram Data File (generic)
7.MDMarkdown Document
8.JSONJavaScript Object Notation file
9.NOMEDIAAndroid No-Media Marker File
10.JPGJPEG Image

Extensões relacionadas

.NOMEDIAAndroid No-Media Marker File
.DLLDynamic Link Library
.TMPTemporary File
.LNKWindows Shell Link (Shortcut)
.PKGmacOS Installer Package
.ETLEvent Trace Log

Ferramentas de arquivo gratuitas

Um identificador de arquivos e conversor de imagens no navegador - tudo funciona no seu dispositivo.

Abrir a caixa de ferramentas

Navegar por extensões de arquivo A-Z