grahamjonesuk grahamjonesuk

Fences 4 will not install properly on Windows 11

Fences 4 will not install properly on Windows 11

Installation runs, but Fences will not load after restart

I have installed Fences 4 (latest version). I have Windows 11 (latest update). 

Fences 4 installation routine runs correctly (it seems) and issues a "need to restart" dialog afterwards.

I restart, the Customize Fences icon is on the desktop and when I double click on that I get a warning saying "Fences does not appear to be loaded. You may need to reinstall Fences".

So, I reinstall Fences.

The error repeats. 

I have uninstalled and reinstalled four times and the error continues. Fences does not load at Startup.

When I look in the Setting for Startup Apps, only Fences Settings is there (and switched on for Startup). Fences itself is not there. 

Any ideas?

38,707 views 33 replies
Reply #26 Top

I have followed your instructions (though I had already done all of that before)

As you can see from the screenshot, even after a clean install only one instance of Fences is loaded

 

Reply #27 Top

Any updates? I have tried everything...! With a clean install on a new and fresh admin account and with a restricted startup, only one instance of Fences appears after installation, not two. 

As I have said, this only happens on this desktop machine and not on my laptop. It can't be a conflict with any other running software as I have eliminated that with the selective startup and the fresh install to a new admin account.

Does this mean there is a conflict with a hardware driver specific to this machine? 

All ideas are welcomed...!

Graham

Reply #28 Top

Quoting grahamjonesuk, reply 27

Any updates? I have tried everything...! With a clean install on a new and fresh admin account and with a restricted startup, only one instance of Fences appears after installation, not two. 

As I have said, this only happens on this desktop machine and not on my laptop. It can't be a conflict with any other running software as I have eliminated that with the selective startup and the fresh install to a new admin account.

Does this mean there is a conflict with a hardware driver specific to this machine? 

All ideas are welcomed...!

Graham
End of grahamjonesuk's quote

Is the PC Windows Pro or Home?  If Pro, I would like to have you run an instance of Windows Sandbox on it:

https://www.thewindowsclub.com/windows-sandbox

Once the instance is running, install Fences on it (it will use one of your activations but you can free it later under your account page). 

Does it then work under it?   

Note, if you kill the instance of Win Sandbox, it will nuke everything and you would need to start over so don't do that until you have verified it works or not.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #29 Top

Aha - we're getting somewhere. Thank you for your suggestion. Fences installs OK and works normally in a Sandbox. 

Graham

Reply #30 Top

Quoting grahamjonesuk, reply 29

Aha - we're getting somewhere. Thank you for your suggestion. Fences installs OK and works normally in a Sandbox. 
End of grahamjonesuk's quote

Then it has to be something installed on the PC or a setting.  What the sandbox does is fire up a base version of the OS.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #31 Top

OK. I'll try working through what it might be. But I have already tried installing in a new user account and using selective startup via msconfig, switching off everything. All the settings I have are identical to the settings I have on my laptop, on which Fences 4 is running fine. So the mystery continues. Thanks for your ideas, though. I will try and work out what is going on and update you when I find out (hopefully).

Reply #32 Top

At long last I have it working. After repeated attempts, taking into account everything said above I was able to install it today. It seems to have been possible following this morning's BIOS update from Hewlett Packard. Not sure why that makes a difference - but it did...! It could explain somehow why Fences worked on my other machines and not this one? Either way, the issue is resolved.

Reply #33 Top

Quoting grahamjonesuk, reply 32

It seems to have been possible following this morning's BIOS update from Hewlett Packard.
End of grahamjonesuk's quote

That was my next thing to try (total lie) ;)

Pleased to hear it is working for you.

Sean Drohan
Stardock Product Lifecycle Manager