See the image - some directories are being miss-reported. A 4 MB folder is showing as hundreds of gigs (larger than the entire drive) and the physical size of the container reflects that.
The odd thing is SpaceMonger does know the true size of the container as the mouseover tooltip correctly reports the size.
This seems like a pretty major bug, can someone please review and fix? I've included OS metatdata in the screen capture.
Hello,
I have forwarded your problem to Stardock Support team for their assistance. Please keep an eye on this thread for any updates. Also please note that Stardock is on Summer Vacation and will be back next week, Monday July 9th.
We appreciate your feedback and patience.
Basj
Stardock Community Assistant.
Hi,
I found this problem with large file sizes too.
There are several weird files, which appear to be very large in SpaceMonger, but in fact, they are small.
Later I have discovered, that recently, Microsoft introduced at least 2 new Reparse Point types, which are similar to Symlinks, but not quite.
I have found some information on google, you might want to have a look at it:
https://lifeinhex.com/running-windbgx-on-windows-7/
https://forum.exetools.com/showthread.php?t=18391
https://bvckup2.com/support/forum/topic/854
http://www.zezula.net/en/fstools/filetest.html
Here are some typical examples.
C:\Users\username\AppData\Local\Packages\SpotifyAB.SpotifyMusic_zpdnekdrzrea0\LocalCache\Local\Microsoft\Windows\Caches\cversions.1.db
is a reparse-point with tag 0x80000018 IO_Reparse_Tag_WCI
Displayed size: 8589934592 B, size in explorer: 16384 B
C:\Users\username\AppData\Local\Microsoft\WindowsApps\MicrosoftEdge.exe
is a reparse-point with tag 0x8000001B IO_Reparse_Tag_AppExecLink
Displayed size: 8589934592 B, size in explorer: 0 B
Yup, same here. Unless SM can handle links (symlinks, hard links, soft links, reparse points, junction points, whatever), it's not very useful.
It's been a couple months since Stardock's vacation ended. Has there been any update on this issue?
Nothing yet that I know off.
Thank you,
Basj,
Stardock Community Assistant
I've had this problem since about 1803 too. But I assumed there would be no fix, as I thought they'd abandoned development (although still happy for me to buy it).
For me, the most obvious problem with with MicrosoftEdge.exe. It's a zero byte file, which must be some sort of link to the real file in the package repository. Not sure if its a hard/soft link, junction, or whatever the Microsoft parlance is.
On my PC, which has 5 user accounts, Edge appears to occupy 2x 8,589,934,592 bytes for each account. That's a total of 86GB! So, my first job is to always hide these 10 files when I use Spacemonger on C:
I really wish I can give you an answer, but no news with regards SpaceMonger that I know off so far.
I have forwarded again this issue to Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.
A temporary workaround for me is to use the Logical Map instead of the Physical Map.
It's been about six months now. Any update on fixing this issue?
Sorry to hear you are having issues.
I don't use the program myself to check it out and now we are in a Holiday Weekend
so I will bring it back up to support when they return , sorry for the delay.
AzDudeStardock Community Assistant
To clarify, the app doesn’t work at all with this Windows 10 bug. The whole purpose of this app (determining file and folder sizes on a drive), hasn’t been working for almost a year with level 1 forum support responses saying ‘I’ll pass this on’ and another 6 months goes by.
Can an you please escalate this to your development team and/or supervisor?
I’m going to request a refund if you don’t fix this within the next few weeks - the level of support on this major issue has been pathetic.
TreeSizes is a free app that does essentially the same thing - care to explain why I paid for your product when it doesn’t work?
Agreed. I've been told for the past eight months that the entire development team is on vacation and they'll be told when they return--then, no news. Companies I've worked at have a support ticket system where a problem (especially one as major as this one) can be logged so that they can be triaged, prioritized, fixed, and released. Unless Stardock manages technical support with Post-It(TM) notes, can someone log this issue in the bug system?
Similar issue: https://forums.stardock.com/489572/page/1/#3738778
SpaceMonger is a $15 product. It does not perform its most basic function. It either crashes or displays wildly inaccurate values. This is not a minor bug--it can't do at all what it says it will do. How do I request a $15 refund?
Another month has passed. Any thoughts from Stardock? Has this application been abandoned and we should give up on ever being able to use what we paid for?
You're probably wasting your breath. Stardock wouldn't give me technical support by email, and directed me here, where they don't give you support either. It's free peer support only, I'm afraid. Shame they won't admit it. Stardock, please prove me wrong.
By the way, what version are you running? There are two versions, depending on which link you click. I'm on 1699, the purchase offered me 1697. I don't know what changed between versions. Might be worth checking. I still have to use the Logical Map, as the Physical Map shows disproportionate usage by multiple copies of Microsoft Edge.
I've got 1699 as well. It seems to be the latest download offered.I've definitely given up on Stardock. After more than a year, I can't imagine they're supporting anything. Their latest newsletter makes it pretty clear they intend to abandon a lot of their under-performing products. I understand the business decision, but I'd prefer it if they were upfront instead of lying for months.
There are some free products out there that are reliable, such as WizTree, WinDirStat, TreeSize, SpaceSniffer, etc.
Yeah. How many holidays do they have a year?!
I have got SpaceMonger 3.0 Build 1711 (2018-11-16) now,from https://cdn.stardock.us/downloads/public/software/spacemonger/SpaceMonger_sd_setup.exeThe bug is still there - many files still show the size 8,589,934,592 bytes. Not only MicrosftEdge.exe, but also many Windows Cache files.
I always have to select each Cache folder and press "H" to hide it.
The SM size reporting issue has been reported and known internally.
It's dishonest to still be taking $15 for this product today, and yet this glaring bug has existed for more than a year with no support. You should withdraw the product or fix it.
This appears to be still broken for me.This is a product people are paying real money for. Ignoring the issue is shocking, frankly.
When will the dev team have a fix? Surely this must have been escalated to immediate priority? If not, why not?
There are many great features available to you once you register, including:
Sign in or Create Account
