Does SpaceMonger actually work?

from Stardock Forums

The tree view thinks I have 52.9 petabytes of storage.

 

 

 

I I closed the app and did another scan, and now I'm using exabytes of storage.

 

Does this app actually work?

stardock software
24,354 views 15 replies
Reply #1 from Stardock Forums Top

Looks like the involved files are Windows AppStore reparse points. When SpaceMonger can't handle them, it gets blown out of the water and any hope of a meaningful space usage summary is lost.

How can I open a support ticket about this? This bug makes the product unusable.

Reply #2 from Stardock Forums Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Start11 - Customize the Start Menu and Taskbar in Windows 10/11.
Reply #3 from Stardock Forums Top

Hi mikeblas,

Quoting mikeblas, reply 1

Looks like the involved files are Windows AppStore reparse points. When SpaceMonger can't handle them, it gets blown out of the water and any hope of a meaningful space usage summary is lost.

How can I open a support ticket about this? This bug makes the product unusable.
End of mikeblas's quote

I've logged your experience here with our team internally.  

Internal Reference: ODNT-1214

Thanks much for the feedback.

Adam McGuinness
Stardock Customer Support Specialist

Reply #4 from Stardock Forums Top

Quoting SD_McGuinness, reply 3

I've logged your experience here with our team internally.  

Internal Reference: ODNT-1214
End of SD_McGuinness's quote
Thank you. What are the next steps?

Reply #5 from Stardock Forums Top
Quoting mikeblas, reply 4

Thank you. What are the next steps?

End of mikeblas's quote

The log (including this thread) is available for us to track and review internally. 

At this time, we have no schedule as to when it would be addressed if an issue is confirmed.

You can keep this thread on your forum Watch List if you like. 

Adam McGuinness
Stardock Customer Support Specialist

Reply #6 from Stardock Forums Top

Quoting SD_McGuinness, reply 5
The log (including this thread) is available for us to track and review internally. 

At this time, we have no schedule as to when it would be addressed if an issue is confirmed.
End of SD_McGuinness's quote
Oh, I see. I wasn't aware that this product wasn't supported.

Reply #7 from Stardock Forums Top

How do you come to the conclusion that "this product wasn't supported"?

Thank you,

Basj,
Stardock Community Assistant

Reply #8 from Stardock Forums Top

Quoting basj, reply 7

How do you come to the conclusion that "this product wasn't supported"?
End of basj's quote
I have reported a high-severity, easily-reproducible bug in the product. A day later, the issue isn't even acknowledge and I have no more information on it than when I first reported the issue, which isn't even confirmed or acknowledged at this point. I'm told that I can't track anything, and maybe (or maybe not) something will be done about it.

Nobody has requested any more information, or offered any workaround or suggestions. Nobody has asked for more information about my configuration or usage.

The issue itself shows very poorly for the product -- a catastrophic failure in a direct and trivial use case. It's as if I'm the only person who's ever tried to use the product, really.

How could I come to any other conclusion?

Reply #9 from Stardock Forums Top

Quoting mikeblas, reply 8

I have reported a high-severity, easily-reproducible bug in the product. A day later, the issue isn't even acknowledge and I have no more information on it than when I first reported the issue, which isn't even confirmed or acknowledged at this point. I'm told that I can't track anything, and maybe (or maybe not) something will be done about it.
Nobody has requested any more information, or offered any workaround or suggestions. Nobody has asked for more information about my configuration or usage.

The issue itself shows very poorly for the product -- a catastrophic failure in a direct and trivial use case. It's as if I'm the only person who's ever tried to use the product, really.

How could I come to any other conclusion?
End of mikeblas's quote

Mike, I understand (and actually share) your frustration. However, your retelling of the experience here seems inaccurate. 

Your post was seen and responded to promptly (3 hours for the 1st response, under 24 hours for the 2nd, and repeated replies after).  If you expect quicker response times from a software developer, please tell me what those expectations are and what other developer you have engaged with that is meeting or exceeding them.

What you reported is a known issue (one Adam and I discussed after he asked me about your initial post).  The internal ticket Adam noted already existed - he added your experience and data to it.

While I would like the issue to be resolved as quickly as you do, as you might suspect, there are competing priorities internally and this issue has, sadly, fallen lower on the list over time.  With your report, it is my hope that it will get renewed attention. 

From now on, if you have more to add to this, please address me directly.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #10 from Stardock Forums Top

Quoting sdrohan, reply 9
However, your retelling of the experience here seems inaccurate.
End of sdrohan's quote
What do you think I got wrong?

Quoting sdrohan, reply 9

While I would like the issue to be resolved as quickly as you do, as you might suspect, there are competing priorities internally and this issue has, sadly, fallen lower on the list over time.  With your report, it is my hope that it will get renewed attention.
End of sdrohan's quote
If it is known that the product is so substantially broken why is it still offered for sale? How long has that been the case?

Reply #11 from Stardock Forums Top

Quoting mikeblas, reply 10

What do you think I got wrong?
End of mikeblas's quote

This, every part is inaccurate. 

Quoting mikeblas, reply 8

A day later, the issue isn't even acknowledge and I have no more information on it than when I first reported the issue, which isn't even confirmed or acknowledged at this point. I'm told that I can't track anything, and maybe (or maybe not) something will be done about it.
End of mikeblas's quote

 

Quoting mikeblas, reply 10

If it is known that the product is so substantially broken why is it still offered for sale? How long has that been the case?
End of mikeblas's quote

The app 'works', just not in all scenarios.

Sean Drohan
Stardock Product Lifecycle Manager

 

 

Reply #12 from Stardock Forums Top



That's weird. Every word of it is objectively correct. Let's dig in to help you understand:

A day later, the issue isn't even acknowledge and I have no more information on it than when I first reported the issue,

 
At the time I wrote that, there was no acknowledgement that an issue existed. I was told that there was no schedule for addressing anything on the conditional "if an issue is confirmed". That is, the issue I reported wasn't confirmed, and therefore not acknowledged. It wasn't until your post, another day later, that this high-severity flaw in the product was acknowledged.


I'm told that I can't track anything, and maybe (or maybe not) something will be done about it.


An internal (only) tracking issue was opened (or updated?) with my input. I can't track any changes to that issue, since it's internal. You yourself reinforced the response that the application may (or may not) be fixed.

Quoting sdrohan, reply 11

The app 'works', just not in all scenarios.
End of sdrohan's quote
If you have to put quotes around "works", then the app doesn't work.

I can't guess what you mean about scenarios. I'm not doing anything special. The blurb for the app says that it will "Scan, Map, and Manage PC and network storage". It abjectly fails scan or map disk usage on both machine where I've tried to run it.

It's a pretty straightforward conclusion to make that, if a company knows of high-severity issues in their product and they aren't fixing it, they're effectively not supporting the product.

 

Reply #13 from Stardock Forums Top

Thank you for the feedback, mikeblas.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #15 from Stardock Forums Top

Hello,
Sorry, but there nothing new to report on this one.

Thank you,
Basj,
Stardock Community Assistant.