If ZimaClient on Windows shows “Permission Required — Authorization is required to proceed with initialization,” do not reset CasaOS or ZimaOS first. Treat it as a Windows client initialization/privilege problem: install the current client, allow Windows UAC and network-driver permissions, verify the ZeroTier dependency, then collect ZimaClient logs if the prompt persists.
The source thread contained only the question and no verified forum fix. Current ZimaClient documentation does not publish a specific “Grant Permission” button for this message, so the safe guide is to troubleshoot the Windows client rather than inventing an authorization workflow.
Install the Current ZimaClient
The current ZimaClient installation guide says to run the Windows installer and includes current troubleshooting steps.
Accept Windows UAC Prompts
ZimaClient installs networking components and background processes. If Windows asks for administrator authorization during installation or first initialization, approve it from an administrator account you trust.
Check the ZeroTier Dependency
Current official troubleshooting says that if installation is stuck, install the current ZeroTier package and confirm internet access, then run ZimaClient again.
Restart ZimaClient After Installation
Exit the tray client completely and relaunch it after any driver/service installation. If the problem began after an incomplete install, reinstalling the current package over the top is safer than editing Windows services manually.
Check Windows Security Software
Endpoint security, antivirus, application-control policy, or a non-admin corporate account can block installation of network drivers/services. If this is a managed PC, you may need the machine administrator rather than a ZimaOS setting.
Test Direct LAN Access Separately
If the NAS is reachable by IP in a browser, the ZimaOS/CasaOS host is alive. A Windows-only Permission Required dialog does not justify reinstalling the server.
Collect the Official Windows Logs
%AppData%\Zima\logsCurrent documentation says to capture screenshots, exit ZimaClient, collect all files in that directory, and send them with a description of the issue.
Do Not Disable Windows Security Globally
Do not turn off Defender, firewall, driver signing, or UAC just to make initialization proceed. Identify the exact blocked service/driver or use an administrator-approved installation.
The connection troubleshooting guide helps isolate the failing layer.
FAQ
Where do I grant ZimaClient permission?
There is no current documented in-app permission switch for this exact message; approve Windows installation/UAC prompts and verify the networking dependency.
Does the NAS owner need to authorize the Windows PC?
Normal device association may still be required, but a first-run “Permission Required” message can also come from local Windows initialization.
Where are ZimaClient logs on Windows?
%AppData%\Zima\logs.
Should I reinstall the server?
No. First confirm the server works by direct IP and troubleshoot the Windows client separately.
