Does my 5 unit license become invalid with fences 5? Do I have to pay for it again? Because right now Fences 4 pestered my about updating, but only to the next version 4. It's not telling me to update to version 5.
christopherweber
(I apologize that this is obviously a duplicate. But I did a search saw a LONG list of posts, and can't click on ANY of them to actually read the post, does not one realize that renders the search pretty much useless) I have a 5 license pack, and have used 3. One really old laptop I am "de-commissioning", and have purchased a new laptop. So I want to uninstall and free up a license before I brain wipe the drive. On the same topic... I also installe
As I said, I got one of those versions working. However, it spent the next few days nagging me to update. I finally did yesterday, and it only says I now have version 4.22. Copyright 2025. So I can't compare it to what I had before. Nor do I know if I could reinstall it (licensewise), since this is a new laptop, I might end up having an issue and re-installing the OS, or even replacing it. I powered down last night (whatever that means in Windows th
Well, I didn't write these myself. I got them from the web site somewhere, a few years ago. Pretty annoying when EVERYTHING on my desktop is gone. Like it's been double clicked to "hide icons", except that wasn't it. Even a ri
[quote who="basj" reply="90" id="3960549"]Forcepoint/Websence [/quote] I've never heard of them. I said this is a new install. I used Fences4-fs-setup_sd-4.exe 4.1.0.6 I installed Fences 2 (Fences2_setup_sd.exe - 9.5.1.0) as I still has an old install and key. (Apparently trying to be honest and use current keys I paid for shot me in the foot.) It is installed on top of Fences 4, but all the UI said is Fences 2. Fences 2 installed. S
I have the same problem. I have an old Dell, running Fences just fine. (which I am about to decommission) I now have a BRAND NEW PC, Windows 10 Pro (19045.5371) 22H2, from the exact same Windows install as the DELL (the Dell is 19045.4412), just a different KEY (Not OEM, it's MSDN). I am not wasting my time repeating all those tests that were told to other people WHICH NEVER WORKED (hack this, registry that, sandbox...). (By the way, this <span style="text-