Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: banger on August 10, 2017, 10:30:50 PM
-
Going to try a reboot first just to see if it is a one off but All versions of DSLStats just close after the first sample on Windows 10 Pro.
-
Exclude the DSLstats installation folder from being scanned.... Used to run it on the server and the same happened...
-
Have rebooted and still no go. There doesn't appear to be a way to exclude folders unless they are blocked by Bitdefender which it isn't.
Some progress I downloaded the self-installer of 6.0.2 and the zip of 6.0.4. 6.0.2 runs ok after an install to my user dir but putting 6.0.4 in the same place just closes after it starts sampling.
Could we have a self-installer to test if Bitdefender is seeing it as a rogue program without an installer of 6.0.4. 6.0.2 seems to be running ok.
-
Upload the file for BitDedender to scan and whitelist.
If they don't allow that, or the ability to exclude files/folders, then I would suggest using a better AV. The inability to bypass a false positive essentially renders am AV useless.
MSE does the same thing with the upload.exe files from within DslStats (upload15.exe, upload16.exe, etc). Uploading the file for them to scan resolves the issue for everyone, which I recently did for upload17.exe, which no longer gets detected by MSE.
-
This is off the BitDefender web site (but it's for Win8, not sure why they would remove it for Win 10?):
To add the folder to the Exclusions list, follow these steps:
Open the Bitdefender window.
- Click the Settings button on the upper toolbar.
- In the Settings Overview window, select Antivirus.
- In the Antivirus Settings window, select the Exclusions tab.
- Make sure Exclusions for files is turned on by clicking the switch.
- Click the Excluded files and folders link.
- Click the Add button, located at the top of the exclusions table.
- Click Browse, select the folder that you want to be excluded from scanning and then click OK.
- Click Add and then click OK to save the changes and close the window.
-
Bitdefender isn't detecting it as a virus (no pop up) so I can't exclude it because bd needs to detect as a virus in the first place. I think this may be a 6.0.4 problem but I would like to rule out the location problem. Up until now, it has been running fine from my archive drive H:\ but now it won't unless I use the installer.
-
This is off the BitDefender web site (but it's for Win8, not sure why they would remove it for Win 10?):
To add the folder to the Exclusions list, follow these steps:
Open the Bitdefender window.
- Click the Settings button on the upper toolbar.
- In the Settings Overview window, select Antivirus.
- In the Antivirus Settings window, select the Exclusions tab.
- Make sure Exclusions for files is turned on by clicking the switch.
- Click the Excluded files and folders link.
- Click the Add button, located at the top of the exclusions table.
- Click Browse, select the folder that you want to be excluded from scanning and then click OK.
- Click Add and then click OK to save the changes and close the window.
This is BD free and although it has an exclusions tab there is now way to add a file/folder. I have scanned DSLStats.exe and it says clean with the on demand scanner so it seems that is not it.
The only thing I changed was the AV and upgrade to 6.0.4. Back on 6.0.2 now.
-
Concerning the questions about the self-installer, this doesn't do anything beyond copying the files to an appropriate location and adding menu entries and a desktop icon. I don't really understand what you meant about using it to check BitDefender's response to the new version, but I certainly won't be able to do that.
The differences between v6.0.2 and v6.0.4 are quite small, and I can't see anything which could account for your experience. I'm afraid that, in the absence of more information, there's not much I can do.
-
I have used Bit Defender for many years, version updated every year, currently running Bit Defender Internet Security 2017, have never had any compatability issues with DSLStats on any program revision or any requirement to add any file exclusions within BD program.
My operating system is Windows 8.1 64 bit running on a desktop PC.
The only ever compatability issues I have had with Bit Defender is with Malwarebytes program, this would periodically cause Windows "blue screen of death", BD recommended disabling Malwarebytes live protection which did cure the issue, I have been able to re-enable live protection again since updating to the current 2017 BD program.
-
@Roseway not to worry I have 6.0.2 working fine. I think it is something to do with directory location which has been mentioned before.
-
@Roseway
I have got 6.0.4 working now.
I changed the following in the ini file.
[snapshots]
Snapshotdir=C:\Users\x_ban\AppData\Local\dslstats\
Dateorder=0
UseHoursperpage=1
Hourspersnapshot=2
Start of recording=0
Start of recording from 1 to 0 and now no crash. I can supply error log and re-enable start of recording. Seems it is something to do with snapshots. Also, my explorer won't reveal hidden folders I click the box show hidden folders but then something unticks it straight away. Maybe DSLstats cant see appdata folder as it is hidden?
Edit: This is not the culprit as it only worked once. I think it is something in the sampling routine. When I turn off autostart then manually press the sample button it just closes. Back to 6.0.2 an error has crept into 6.0.4.
-
As I said before, I can't reproduce this. Before I released v6.0.4 I ran it for 24 hours on a Win 8.1 system with all monitoring options enabled and a selection of snapshots, to check that it had really fixed the error related to snapshots of average errors. If DSLstats closes as soon as you press the green button, then it's nothing to do with the snapshots anyway.
You believe that it's something to do with the sampling routine, but nothing changed between 6.0.2 and 6.0.4 in that area of the program.
I'm sorry, but there's really nothing I can work with here. I believe that it's something to do with your setup, very possibly related to BitDefender.
-
I will test 6.0.4 later today if it helps as I also run win 8.1.
-
6.0.4 has been running here under Win 8.1 for some days now with no problem.
-
I have found the problem. If I untick upload to MWDS then no crash so it must be something to do with the new upload routine. I unticked all the options in MWDS Config but no difference until I unticked Upload then no crash. So it must be something to do with the new upload program?
-
I appreciate that you're trying to find the cause, but the upload program is the same in v6.0.2 and v6.0.4. Version 17 of the upload program was introduced in v6.0.2. The only change that affected MDWS uploads was the addition of HEC's to the uploads. But that only involved the copying of two values from one location to another, and if I'd got that wrong there would be an error message, it wouldn't cause the program to close abruptly.
That's the difficulty in understanding this problem. The small number of coding changes between the two versions wouldn't cause the program to close abruptly, unless I'd done something really gross. If this were the case, it would affect every user, but it doesn't.
-
Banger, did you by any chance switch the upload16.exe and the upload17.exe and rename it? This was a quick workaround discussed in another DslStats thread recently.
It's the only thing I can think of if both versions should have the same upload17.exe file, and only 1 is crashing.
Try overwriting the upload file from DslStats 6.0.4 with the working version from 6.0.2 and see if it still crashes when uploading to MDWS.
It sounds like the files have either been switched, or an AV exclusion has been added for the 6.0.2 directory that hasn't been added for your 6.0.4 directory.
-
Banger, did you by any chance switch the upload16.exe and the upload17.exe and rename it? This was a quick workaround discussed in another DslStats thread recently.
It's the only thing I can think of if both versions should have the same upload17.exe file, and only 1 is crashing.
Try overwriting the upload file from DslStats 6.0.4 with the working version from 6.0.2 and see if it still crashes when uploading to MDWS.
It sounds like the files have either been switched, or an AV exclusion has been added for the 6.0.2 directory that hasn't been added for your 6.0.4 directory.
That fixes it John. Copying upload17.exe to the 6.0.4 dir allows it to upload successfully so something has happened to upload17.exe in 6.0.4.
-
There's only ever been one version of upload17.exe, and the identical file is included in the downloads for v6.0.2, 6.0.3 and 6.0.4. So I don't know what went wrong on your system, but if it's now working properly then I'm happy. :)
-
Something to do with permissions?
-
Windows filesystems don't have any support for permissions in the way that Unix-type systems do. So long as the file can be seen by the user, and has a .exe extension, then Windows will run it.
-
Hi
I could be wrong sorry, but UAC (user access control) maybe stopping it
Do you start dslstats with run as administrator or for a test, could you turn off UAC in windows
As I said, I could be wrong so apologies in advance
Many thanks
John
-
possibilities are
1 - any cloud service with 3rd party a/v vendors that use a trust system to allow executables
2 - microsoft's own cloud service aka smartscreen on win8 and win10 this is system wide.
3 - anti executable such as software restriction policies, by default this is disabled so wont be the cause if its never been used.
4 - anti exploit protection, this is where anti exploit software hooks on to running programs to enforce things like ASLR, this can cause programs to not work. Personally I dont believe dslstats to be affected by this but I cannot say this for sure across every anti exploit software.
dslstats doesnt require UAC so wont be that, unless you accidentally ticked the box to run as administrator in the file properties.
-
UAC is off but that wouldn't make any difference as I moved the 6.0.2 upload17.exe to the 6.0.4 folder. I am not quite sure what has happened other than a cockup on the DSLStats front but all is working now on 6.0.4 and it has been up for a few hours.
-
One other thing I have noticed is that if you set graph backgrounds to black they all change except the G.INP graph. Have I missed a setting somewhere?
-
No, you're right. That's an omission on my part. It will be corrected in the next release.
-
Many thanks, great program and thanks for spending your free time doing it. :)
-
Thank you :)