Hi,
I have created my filesystem as a service, which have been working fine until I tried this on Windows 2025, where it fails to start without any clue of what is wrong.
My filesystem executable is not event executed at all?
I tried to pass my error through chatGpt, but that give me hint that having my filesystem started as a service, is no longer working in windows 2025 (According to AI).
Their advice is to go with launcher-x64 code?
Is it true that these code is no longer working on windows 2025?
if (!NT_SUCCESS(FspLoad(0)))
{
debug(-1,"():FspLoad:LEAVING:return ERROR_DELAY_LOAD_FAILED",-1);
return ERROR_DELAY_LOAD_FAILED;
}
debug(-1,"():FspLoad:LEAVING:return FspServiceRun()",-1);
return FspServiceRun(L"" PROGNAME, SvcStart, SvcStop, 0);
AI also said that the registry PATH has changed?
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\WinFsp\Services\SPFS
Or should it be the 64bit PATH, as my filesystem is 64bit code?
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WinFsp\Services\SPFS
Or should it be instanciated? as AI said?
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WinFsp\Services\SPFS\X
Or how do I make the filesystem persistent after logout/reboot?
I used to have a service dispatcher for this, which have been working fine on older windows with SvcMain function etc.
Do you have any tips?