Usage meter javascript error

[Vampy]

A javascript error occured in the main process.  Uncaught exception:

Error: Error parsing your configuration file:  [C:\Users\Vampy\AppData\Roaming\HughesNet Usage Meter\status-meter.config]: Unexpected Token

I tried uninstalling and reininstalling and got the same thing.  Any suggestions ?  Thanks in advance for any help.

[GabeU]

@Liz

@Amanda

Is there any way that one of you could un-accept the accepted solution for this error?  It's not the correct fix, and it gives steps concerning Java, which has nothing to do with this error.  

[Vampy]

While you say my fix doesn't work I've had to do it at least 10 times and it's always worked for me.  I haven't been back to this thread since I started it and see there are 13 pages of the meter problem since I left.  I am still having problems with it but not as often now.  I used to have to do this weekly and now it's every few weeks.  I'm looking through the fixes to see what you all have found.  If this meter is somehow fixed no one will be looking through this thread.  Now they know there's a problem with it.

[maratsade]

What fix do you use?

Vampy wrote:

While you say my fix doesn't work I've had to do it at least 10 times and it's always worked for me.  I haven't been back to this thread since I started it and see there are 13 pages of the meter problem since I left.  I am still having problems with it but not as often now.  I used to have to do this weekly and now it's every few weeks.  I'm looking through the fixes to see what you all have found.  If this meter is somehow fixed no one will be looking through this thread.  Now they know there's a problem with it.

---

[MarkJFine]

There are a lot of people that think you can just shut a machine off without shutting down the operating system.

Also, a lot of desktops aren't on battery backups and lose power before the operating system is shut down.

The problem is known. It's always been known. I think it was even proven to happen whenever one of the above happens it corrupts the cache files which are never removed just by uninstalling it - UNLESS the user physically deletes the remnants before re-installing.

So again, please understand, it's not the install/re-install process that fixes it. It's the deletion of the corrupt cache files themselves that actually fixes it. The install/re-install part itself does nothing but add extra steps and is redundant.

[maratsade]

I've been using a different method that works for me on Windows 10: I open task manager, look for the instance(s) of the meter, end the task(s), close Task Manager, and the meter then opens just fine.  

[GabeU]

---

@maratsade wrote:

I've been using a different method that works for me on Windows 10: I open task manager, look for the instance(s) of the meter, end the task(s), close Task Manager, and the meter then opens just fine.  

---

I've had that work for me a couple of time, but the majority of times it didn't.  Still, I do try that once in a while when it happens.  

It happens often enough that I finally just created a shortcut to the Roaming folder on my desktop.  That way I can simply click the shortcut and delete the HughesNet folder from there.  No changing the folder view and having to go through all the steps to get there.  And that it happens often enough for me to think of creating the shortcut is crazy.  It hasn't happened in a while, though, as I haven't lost power for at least a few months... knock on wood.  🙂  

[maratsade]

It has worked for me every single time, so far (knock on wood). 

Great idea creating a shortcut to the folder!

[C0RR0SIVE]

I ended up writing a short article and batch file for this issue, got tired of people complaining about it... Batch file does it for you the fastest, just a quick run as administrator, and it will remove the files for ya.  Really shouldn't even need to run it as an administrator.  File was tested in Win10, have no idea if win7/8 will support it.

https://chucksbasix.com/2019/04/23/hughesnet-usage-meter-startup-errors/

[GabeU]

@Vampy 

While your fix may somehow be working for you, it's not for the majority of people who have had the problem and tried your fix, or at least those who have asked for further help.  This is why I requested that the chosen solution be unmarked as such.

[Rafela]

This solution worked beautifully for me.   thank you for the assist!

[GabeU]

---

@Rafela wrote:

This solution worked beautifully for me.   thank you for the assist!

---

You're very welcome.  I'm glad you found the solution and it worked for you.  🙂