NetExtender 10.3.1 Will Not Install on latest version of Windows 11 Enterprise
Sam_Bennett
Newbie ✭
Several new laptops are running Windows 11 and cannot install NetExdender 10.3.1.
I have tried both the 64-bit .exe and the .msi versions of the installer.
When I try to install the .exe as administrator, I get the error "The installation of SonicWall NetExtender has failed, and the process will be rolled back." I select the "Ok" button and it goes away.
When I try to inst all the .msi, I get the error "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item." I select the "Ok" button and the installation seems to proceed and finish. I select the "Finish" button and NetExtender launches. However, it says "SonicWall NetExtender Service is not running! Please restart system or contact IT for support." However, after a few seconds, the first line changes to "SonicWall NetExtender Service does respond!"
I have also run the NetExtender Cleaner Tool and rebooted several times. I have changed the permissions on the "C:\Program Files\SonicWall" folder to make sure I have full control. I have searched the registry for SonicWall and NetExtender and deleted all entries.
I am at a loss as to how to correct this problem, and I have remote workers who cannot do many of their tasks.
Any help anyone can provide is appreciated.
Answers
I think maybe you can check your antivirus software first. Disable them and try again to test?
Same issue here, and after an hour of messing with everything else, Netextender 10.2.341 worked for me!
Same issue here (but W11pro instead of enterprise). Worked fine on my laptop. 2nd laptop I tried would not install under the user using UAC or as my admin account on multiple attempts. Paused AV, no change (I use the same AV on mine and had no issue).
10.2.341 installs fine, but we have had issues with needing to reinstall that version occasionally. On that version, we've had multiple users where the "service" stops working, and it shows it is version 0.0.0 in the about area. Trying to start switching folks to 10.3 which seems to indicate it resolved that issue according to the release notes.