Windows Enterprise

Hello

I have been using fences for several years now , have had issues with Fences on Windows 10 Pro ,like not loading after windows boots up and not allowing icons to show with out re-loading fences again.

But I have Windows 10 Enterprise and if I load fences and try to create a fence then all of my icons are locked in place and can not move any of them. Only get circle with line thru it tell me to stop this can not be done.

If I unInstall fences and reboot all is fine with my icons , can move them where I want them.

Anyone else have this issue?

I have turned in support ticket several days ago but have not heard from support as of yet.

10,832 views 13 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Please check if your fences is locked. If it is,  please unlock it and try again. Right click anywhere on desktop -> view -> Lock Fences. Try it and report back

Thanks

Basj,
Stardock Community Assistant.

Reply #2 Top

Basj

Perhaps I did not make myself clear as to the problem. It is not that I can not move a Fence the issue is all of my ICONS on the desktop are immovable as soon as I create a fence; it matters not whether an ICON is inside or outside of the Fence.

Hope this makes it a bit clearer

I need an answer to this or Fences is useless to me

Thanks

Reply #3 Top

Hello

Would you Please try this PURGE: https://forums.stardock.com/486084/fences-support-faq#reinstalling

Reboot and ReInstall the latest version from your account https://store.stardock.com/myaccount/products/

Reboot and test and report back here , also make sure that you have Fences Locked ( unchecked ).

 

AzDude
Stardock Community Assistant

 

Reply #4 Top

What is it you want me to try? I don't see anything on site that shows what you ask and if I don't know what it is going to do I will not try it

Thanks

Reply #5 Top

Hello,

Sorry to hear you are having issues.

Sorry My Mistake , I put the wrong link above ( corrected the link now )

a Purge is a different kind of uninstall .

So pugre reboot reinstall reboot and test and report back here .

make sure as in reply #1that Fences Locked is UnChecked ..

 


AzDude
Stardock Community Assistant

Reply #6 Top

I have done as you asked and it makes no difference.

I what to ask a question?

Can one have a Virtual disk running Windows 10 at the same time the host is running Windows 10. And if so can you have fences running on both Host and Virtual at same time?

I do think that is my issue because like I said as soon as I install Fences and activate the program all of my desk icons are locked in place , even though I have created no "Fences" at all

And if this is the case how do I fix that issue because I want Fences to run on both platforms at same time , because my virtual machine is my test arena before I commit any changes on host

Thanks

Reply #7 Top

Quoting mntlvr, reply 6

Can one have a Virtual disk running Windows 10 at the same time the host is running Windows 10. And if so can you have fences running on both Host and Virtual at same time?
End of mntlvr's quote

Yes. I have both VM and actual systems running on both Windows 10 and Fences work just fine on both. I am using VMWare Workstation 15 Player.

Please try the cleanboot steps mentioned here : https://forums.stardock.com/486084/fences-support-faq#reinstalling

This should tell us if there is compatibility issue with other programs in your system.

Would also like to know if the issue on both systems or just the VM system?

Thank you,

Basj
Stardock Community Assistant.

Reply #8 Top

Clean boot was tried several times no go.

I have resolved the issue I think by using two different versions for each machine. I am using VMWare 15 and I downloaded Fences 3.0 today and installed it and this version works , If I install same version that is on my host machine screen is locked up can not move any icons or crat and fences. So something in newer version solved my issue for now

Thanks

Reply #9 Top

Great, glad you solved it.

Just as side note, I am running Windows 10 V1909 and Fences V3.0.9.11 on both system without issues on Fences.

Thank you,

Basj
Stardock Community Assistant.

Reply #10 Top

Quoting mntlvr, reply 8

Clean boot was tried several times no go.

I have resolved the issue I think by using two different versions for each machine. I am using VMWare 15 and I downloaded Fences 3.0 today and installed it and this version works , If I install same version that is on my host machine screen is locked up can not move any icons or crat and fences. So something in newer version solved my issue for now

Thanks
End of mntlvr's quote

The only way I can see that being an issue is if the VM is trying to use running resources/apps from the host - meaning, the VM was set to use Fences from the host PC. 

As your solution indicates, having each use their own install of Fences should resolve that. 

Sean Drohan
Stardock Support Manager

Reply #11 Top

Well I don’t know how VMWare was doing that but running 2 different version an old version on the host and a newer version on the virtual helped because if your theory is correct having 2 different versions would not help for some reason the fence app is locking up part of windows explorer.

i went into task manager and stopped Explorer then restarted it and the icons on the desk top were no longer locked out so that concludes it has to do with Fences and Explorer not getting along

but if i reboot the host the same issue happens????????

screen icons are frozen in place again

Reply #12 Top

Quoting mntlvr, reply 11

i went into task manager and stopped Explorer then restarted it and the icons on the desk top were no longer locked out so that concludes it has to do with Fences and Explorer not getting along
End of mntlvr's quote

Fences runs in the WinExp process. 

I dont want to un-fix what you have working now so I am not included to dig but I am not certain I have a full understanding of how you have Fences installed (prior) and how that might have related to the issue.

Sean Drohan
Stardock Support Manager

Reply #13 Top

Well i am still digging into it just seems very strange that it has happened to me on Windows Enterprise running in VMWare and now with Windows 10 workstation????