Thank you for your suggestion, however, I have already tried that and it did not fix the meter.
I can go to the System Control Center through my browser, is there something there I should
It is odd, that this update does not work, yet the previous one worked just fine.
Any other suggestions?
Since the steps I provided did not work and Avast already allows the status meter through, it wouldn't hurt to follow the instructions that @MarkJFine posted on the first page (deleting the HughesNet Usage Meter folder). Just make sure the Status Meter is closed before deleting the folder, then try opening the meter again after the folder has been deleted. Let us know if that works!
Just for clarity: You should delete "C:\Users\[your User name]\AppData\Roaming\HughesNet Usage Meter\" where you replace [your User name] with <drumroll> your user name on the computer.
If you delete "C:\Program Files\HughesNet Usage Meter\" instead, it will delete the application, and there's no reason to do that.
I have been running version 184.108.40.206 since I purchased this new computer. No problems
After being pestered to download the latest version (220.127.116.11), the program can no longer find the HUGHESNET MODEM.
I uninstalled the version running and downloaded and installed 18.104.22.168. Same problems.
I uninstalled version 22.214.171.124 and re-installed 126.96.36.199. Works just fine.
Windows OS Version: 10.0.16299 N/A Build 16299
Fortunate for me, I have the original downloads on a backup drive.
Did you try altering the settings mentioned in Amanda's post on the previous page?
I still think that the two users are experiencing a firewall problem.
I saw the error message on the taskbar once myself after the upgrade from v6.1.1 to v188.8.131.52
Usage meter IS running to generate that message on the task bar next to the network icon
I suggest be absolutely sure that the NEW version is not being blocked by checking the firewall logs.
here's a snippet of mine.
Pestered to upgrade the HughesNet Usage Meter, I accepted the request. Message displayed 'A HUGHESNET MODEM CANNOT BE FOUND."
1. Chose settings. Unchecked the Use Default Modem address and saved it. No change of status. Changed the modem address to the address of the modem which I can access from my browser (which is the same as the default.) Saved it and no change.
2. Looked for solutions on the internet. One suggestion was to remove the directory under appdata/roaming/HughesNet Usage Meter/Cache. No change of status.
3. Uninstalled HughesNet Usage Meter and downloaded the latest version. No change.
4. Uninstalled HughesNet Usage Meter and re-installed version 184.108.40.206. This still works.
5. Upgraded the HughesNet Usage Meter from the app. Unable to find the mode.
6. Uninstalled HughesNet Usage Meter and downloaded the latest version.
Im assuming that this is still the same GreyFox who commented yesterday,
What port needs to be opened for HughesNet Usage Meter? The older version continues to work.
I dont know, but the answer to your question would be in your firewall history (logs).
I am just a user (not tech support)
Amanda and @GabeU are BOTH very good at solutions, but They could be in the pacific time zone, very early there now.
Grey Fox, please be patient.
Your solution might be as simple as "allowing" HughesNet Usage meter to access the modem.
confirm that your security rules are allowing version 220.127.116.11 to pass information to your local network.
Of course you would have to install it again.
I suspect that v 6.7 announces itself a little different than v 6.1.1 does.
could be why the old version still works and the new one is blocked.
Same GreyFox. HughesNet made me change my User ID because the one I started with is taken.
I removed the power from the modem, shut down this PC, waited ten minutes of more and restarted. Usage Meter 6.7 still fails. From the status-meter.log: "modem: Call to http://192.168.0.1/getdeviceinfo/info.bin failed."
uninstalled 6.7. Re-installed 6.6.1. Works just fine. Nothing in the status-meter.log.
I will ignore the messages to upgrade.
If it works, don't fix it.
Did it work? Yes.
Did you fix it? Yes.
Does it still work? No.