Tserith / Parasite

Compact MBR Bootkit for Windows
44 stars 14 forks source link

VS2022 Error #4

Closed badboycxcc closed 2 months ago

badboycxcc commented 2 months ago
>Inf2Cat task was skipped as there were no inf files to process
2>------ 已启动全部重新生成: 项目: Parasite, 配置: Release x64 ------
2>make: Nothing to be done for 'all'.
2>install.c
2>E:\Code\Parasite-git\phnt\ntzwapi.h(2123,45): error C2146: 语法错误: 缺少“)”(在标识符“PartitionInformationClass”的前面)
2>(编译源文件“install.c”)
2>E:\Code\Parasite-git\phnt\ntzwapi.h(2123,45): error C2061: 语法错误: 标识符“PartitionInformationClass”
2>(编译源文件“install.c”)
2>E:\Code\Parasite-git\phnt\ntzwapi.h(2123,45): error C2059: 语法错误:“;”
2>(编译源文件“install.c”)
2>E:\Code\Parasite-git\phnt\ntzwapi.h(2123,70): error C2059: 语法错误:“,”
2>(编译源文件“install.c”)
2>E:\Code\Parasite-git\phnt\ntzwapi.h(2126,5): error C2059: 语法错误:“)”
2>(编译源文件“install.c”)
2>main.c
2>E:\Code\Parasite-git\phnt\ntzwapi.h(2123,45): error C2146: 语法错误: 缺少“)”(在标识符“PartitionInformationClass”的前面)
2>(编译源文件“main.c”)
2>E:\Code\Parasite-git\phnt\ntzwapi.h(2123,45): error C2061: 语法错误: 标识符“PartitionInformationClass”
2>(编译源文件“main.c”)
2>E:\Code\Parasite-git\phnt\ntzwapi.h(2123,45): error C2059: 语法错误:“;”
2>(编译源文件“main.c”)
2>E:\Code\Parasite-git\phnt\ntzwapi.h(2123,70): error C2059: 语法错误:“,”
2>(编译源文件“main.c”)
2>E:\Code\Parasite-git\phnt\ntzwapi.h(2126,5): error C2059: 语法错误:“)”
2>(编译源文件“main.c”)
Tserith commented 2 months ago

This project was tested with VS2019. If you wish to upgrade the VS project, platform toolset, or WDK, you may need to update phnt and satisfy any errors created from it. Issue #3 will also be relevant for VS2022.

badboycxcc commented 2 months ago

I used a driver developed with vs2022. After disabling the driver signature, a blue screen error occurred when loading. Can I only use vs2019 for development?

badboycxcc commented 2 months ago

vs2019 compiles the driver to generate an obj file, but there is no sys, is it a linker problem?

Tserith commented 2 months ago

Did you try setting the driver digest algorithm as described in #3?

That would suggest a linker issue, yes. VS2022 could be used, but it may require some changes. However, I am not updating this project as it is a proof of concept.

badboycxcc commented 2 months ago

Use, I have used the abstract algorithm.

badboycxcc commented 2 months ago

Can you give me an email address? I want to have an in-depth exchange with you. I think this understanding of this project is a good learning opportunity.

badboycxcc commented 2 months ago

Could it be a problem with the WDK or SDK version? Can you give me more environmental information?

badboycxcc commented 2 months ago

SDK:https://developer.microsoft.com/en-us/windows/downloads/sdk-archive/ WDK:https://learn.microsoft.com/en-us/windows-hardware/drivers/other-wdk-downloads#step-2-install-the-wdk

badboycxcc commented 2 months ago

It has been successfully compiled with VS2019, but the test failed in Windows 10, and the Windows version is entered.

Microsoft Windows [版本 10.0.19044.4529]
badboycxcc commented 2 months ago
截屏2024-09-05 下午10 30 04
badboycxcc commented 2 months ago

Windows 10 21H2 MBR 20240906-103205

badboycxcc commented 2 months ago

Windows 10 21H2 TCE-metal problem solving