Hello

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

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

also uninstall Space Monger and reboot and reinstall from your account Not ODM.

AzDude
Stardock Community Assistant

"AzDude"
Hello
Would you Please try this PURGE for Fences : https://forums.stardock.com/486084/fences-support-faq#reinstalling
Reboot and ReInstall the latest version from your Stardock account not ODM:  https://store.stardock.com/myaccount

    Ran the .bat file for Fences, Rebooted, and Reinstalled (Not from ODM):  Fences 3.0.9.11 is running;

       ODM still shows a prompt to Install Fences 3, Version 3.09.11;  although it also shows Fences 3.09 as INSTALLED.

       Again, this is a minor glitch: irritating to have the prompt to install the update, but otherwise does no harm.

    also uninstall Space Monger and reboot and reinstall from your account Not ODM. 

       SpaceMonger is still not happy: installed it outside of ODM, filled in license key when prompted, and program seemed to work OK (Scanned a Drive, and did NOT Force Close).

       HOWEVER: upon exiting SpaceMonger it "disappeared" - does not show up as installed under ODM; Win10 search does not find it; NOR does it show under the Control Panel - Programs & Features list.

        Ideas??

I've installed SpaceMonger standalone--outside of ODM. I scanned C:\Users\. The sizes were incredibly wrong (because I don't have 1.4 exabytes of data or a file that's 57,000 gigabytes in size), but that's in another thread. I tried resizing the window and using the Treemap. Then SM crashed.

I'd happily send you the crash.log file, but the support link in the window that appears sends me to the Multiplicity page--not a Support page where I can upload a crash report. Hopefully the first few lines will help. (Another crash was a divide-by-zero failure but this overwrote the first crash log.)

SpaceMonger v3.0 Build 1699 / 20150327-1-F6E5A3CE

SpaceMonger caused an Access Violation (0xc0000005) 

in module SpaceMonger.exe at 0023:00c3a447.

Exception handler called in Primary Thread.

Error occurred at 8/31/2018 18:03:40.

D:\OneDrive\Applications\SpaceMonger\SpaceMonger.exe, run by Stefan.

Operating system:  unknown Windows version (6.2.9200).

8 processor(s), type 586.

49% memory in use.

2048 MBytes physical memory.

2048 MBytes physical memory free.

0 MBytes paging file.

0 MBytes paging file free.

2048 MBytes user address space.

1892 MBytes user address space free.

Read from location 00000018 caused an access violation.

It's been about five months. Has anyone investigated this issue? Is this product not supported?

It's been a month since the most recent request for an update. Is everyone still on holiday weekend? It's been over six months since the problem was reported, and no one's even acknowledged it's an issue.