Is it possible to install and use Harden-Windows-Security completely offline?

[ikarisan]

Hi!

Is it possible to install and run the Harden-Windows-Security App on a system that is air gapped from the internet?
Or is it possible to build a portable version from the source zip file?

Thank you very much.

[HotCakeX]

Hi,
Yes, of course. The script to automatically build the app and all of its sub-components is here. That's the same script used by GitHub action to build it and upload it to Microsoft Store.

[ikarisan]

Oh, thanks! Did not see this. But it is not working for me :(
This is what I get:

`
[...]
info NETSDK1057: You are using a preview version of .NET. For more information, see: https://aka.ms/dotnet-support-policy

DISMService failed with 221 error(s) and 3 warning(s) (4.6s)
→ X:\Develop\Software\Allgemein\Harden-System-Security\Harden-Windows-Security-main\AppControl Manager\eXclude\DISMService\bin\arm64\Release\net10.0-windows10.0.26100.0\win-arm64\DISMService.dll

LINK : warning LNK4266: Missing load configuration symbol for image built with /DEPENDENTLOADFLAG.

LINK : error LNK2001: Unresolved external symbol "wmainCRTStartup".

Runtime.WorkstationGC.lib(handletablescan.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(gcscan.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(gchandletable.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(handletablecore.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(gceewks.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(gcwks.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(GcEnum.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(objecthandle.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(gcconfig.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(handletable.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(PalMinWin.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(yieldprocessornormalized.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(gcenv.ee.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(RestrictedCallouts.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(StackFrameIterator.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(threadstore.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(startup.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(CoffNativeCodeManager.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(RuntimeInstance.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(EHHelpers.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(HandleTableHelpers.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".
Runtime.WorkstationGC.lib(FinalizerHelpers.cpp.obj) : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".

DISMService.obj : error LNK2001: Unresolved external symbol "__guard_check_icall_fptr".

[...]

C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\lib\x86\LIBCMT.lib : warning LNK4272: library machine type "x86" conflicts with target machine type "ARM64"
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\lib\x86\libcpmt.lib : warning LNK4272: library machine type "x86" conflicts with target machine type "ARM64"
bin\arm64\Release\net10.0-windows10.0.26100.0\win-arm64\native\DISMService.exe : fatal error LNK1120: 36 unresolved externals
C:\Users\shinji.nuget\packages\microsoft.dotnet.ilcompiler\10.0.0-rc.1.25451.107\build\Microsoft.NETCore.Native.targets(396,5): error MSB3073: The command ""C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\link.exe" @"obj\arm64\Release\net10.0-windows10.0.26100.0\win-arm64\native\link.rsp"" exited with code 1120.
`

[HotCakeX]

@ikarisan i've verified the build script and it's correct. It successfully builds the MSIXBundle simply just by pasting it in PowerShell.

Works on GitHub action runner successfully, and I just completely tested it on a brand new Azure VM.

Any problem you're experiencing must be on your end.

[hugobelugo]

Hi!

Is it possible to install and run the Harden-Windows-Security App on a system that is air gapped from the internet? Or is it possible to build a portable version from the source zip file?

Thank you very much.

I have a similar problem.

I was able to install and run it, but I can no longer find the offline mode.

Is there also a way to add the path for LGPO, M365, and Microsoft Baselines in the new version? I can only find the option with “Protect-WindowsSecurity -GUI -Offline” in an older version.

[HotCakeX]

@hugobelugo

Thanks for the suggestion, I implemented it and you'll be able to use it in Harden System Security version 1.0.15.0. More info here => #887

There is no problem with building the app either, as you can see I just built it from the same script I mentioned above => https://github.com/HotCakeX/Harden-Windows-Security/actions/runs/18399671718

The build script and its instructions detailed here are correct => https://github.com/HotCakeX/Harden-Windows-Security/wiki/Harden-System-Security#how-to-build-the-harden-system-security-locally

There is no longer a need for LGPO in the new Harden System Security app, it has a completely different internal mechanism.