Installationsproblem

Discuss new features and functions
Posts: 1
Joined: 11 Aug 2022

Günther Schumann

https://translate.google.com
After the program starts, the following message appears, see appendix.

Please help, thanks.
You do not have the required permissions to view the files attached to this post.
User avatar
Site Admin
Posts: 7567
Joined: 9 Dec 2007

Zenju

This doesn't look like it's the latest FFS version.
Posts: 1
Joined: 20 Aug 2022

redd

ffs.png
Both of the Windows donation editions (v11.23 portable and not) linked in the donation email kick out this error when running FreeFileSync.exe post installation. Just to be clear, this prevents use of the software. The process terminates immediately after clicking OK.
edit: the fix, for me at least, was to enable and start the Windows Management Instrumentation service. Device telemetry I guess huh? Might wanna add that into the list of donator 'benefits' on the FAQ...
You do not have the required permissions to view the files attached to this post.
User avatar
Site Admin
Posts: 7567
Joined: 9 Dec 2007

Zenju

Fixed!
Posts: 1246
Joined: 8 May 2006

therube

What was the issue?
User avatar
Site Admin
Posts: 7567
Joined: 9 Dec 2007

Zenju

What was the issue? therube, 22 Aug 2022, 18:50
        if (hr == WBEM_E_NOT_FOUND ||
            hr == E_NOINTERFACE    ||
            hr == HRESULT_FROM_WIN32(ERROR_SERVICE_DOES_NOT_EXIST) ||
            hr == HRESULT_FROM_WIN32(ERROR_SERVICE_DISABLED) ||
            hr == HRESULT_FROM_WIN32(ERROR_SERVICE_NOT_IN_EXE) || //https://freefilesync.org/forum/viewtopic.php?t=8140
            hr == RPC_E_INVALID_HEADER, //broken WMI: https://docs.microsoft.com/en-us/answers/questions/146551/wmic-stopped-working-on-windows-10-2004.html
            hr == WBEM_E_INVALID_NAMESPACE) //system corruption? https://freefilesync.org/forum/viewtopic.php?t=9260
            throw SysErrorWmiUnavailable(formatSystemError("IWbemServices::ConnectServer", hr));
"hr" is HRESULT_FROM_WIN32(ERROR_SERVICE_DISABLED), but the exception is not thrown. Why? I actually had to debug to see the typo. And there's not even a compiler warning about it...