[code_g33k]

Does anyone know how I can find

Code

include \masm32\include\windows.inc

include \masm32\include\kernel32.inc
include \lib\masm32\lib\kernel32.lib

1>src\myshellcode.asm(15): fatal error A1000: cannot open file : windows.inc
1>C:\Program Files\Microsoft Visual Studio\18\Professional\MSBuild\Microsoft\VC\v180\BuildCustomizations\masm.targets(70,5): error MSB3721: The command "ml.exe /c /nologo /Zi /Fo"RxBot\Debug\myshellcode.obj" /W3 /errorReport:prompt /Tasrc\myshellcode.asm" exited with code 1.

I can't find this file anywhere. Visual Studio 2022 has a assembler in it but i need to find this missing file windows.inc. Anyone know where I can locate it?

[LiNixx]

Those files are included in the MASM32 SDK.

The problem is that you’re compiling with ML, which is Microsoft’s macro assembler from Visual Studio.
ML doesn’t come with any of the MASM32 include files, so it can’t find things like windows.inc.


You need to install MASM32 toolchain and either compile inside the MASM32 environment or point Visual Studio’s include and library paths to the MASM32 include and lib folders. Otherwise ML will keep throwing that error because those files aren’t part of the Visual Studio toolchain.

[newQuery]

windows.inc isn't part of Visual Studio. It belongs to the MASM32 SDK.

Download: Grab the kit at masm32.com.
Install: Deploy to C:\masm32 (don't use Program Files).
Link: Add C:\masm32\include to your Visual Studio Project Properties -> Microsoft Macro Assembler -> Include Paths.

Target x86 only. Happy coding.

[HFDone]

MASM is old and outdate use NASM or FASM

[code_g33k]

MASM is old and outdate use NASM or FASM

I actually put nasm back in C:\

Code

C:\Users\rooth>nasm --version
NASM version 3.01rc9 compiled on Oct 10 2025

I plan on learning asm fullest, i bought a book from amazon.

[Terry A. Davis]

I actually put nasm back in C:\

Code

C:\Users\rooth>nasm --version
NASM version 3.01rc9 compiled on Oct 10 2025

I plan on learning asm fullest, i bought a book from amazon.

If you're specifically doing ASM but calling Win32 stuff, why not skip the middleman and just learn C++ through the eyes of Win32?

[code_g33k]

If you're specifically doing ASM but calling Win32 stuff, why not skip the middleman and just learn C++ through the eyes of Win32?

i'm interesting in hardware coding. C++ didn't start from nowhere I believe. assembly deals directly with hardware and memory management that is crucial to learn when low level programming.