I did some digging and its a known false positive when wrapping a powershell script into a exe. The way around it is to sign the exe with a cert that costs $400 a year. I only got it to trigger on my own machine after uploading and downloading it, stayed up until midnight trying to see what the hell, then made a decision to just pull the binary entirely as it's not really needed and goes back to my "everything is exposed" philosophy regarding this utility.
Opening the exe in a text editor will look like an exe most likely, unreadable.
No thanks. I'll just pull the exe, leave the bat which functionally is identical to the exe, and not pay money to avoid false detection. It's a script anyways and that's how it should live until ported to something appropriate.
If anyone wants to make their own, the Garmin fit sdk has the .jar and .BAT files, the timestamp from device is 20 years and 4 days slow, weight in grains is represented in a whole number in raw csv so idivide by 10, min, max, avg are recorded in the raw csv, speed is MM per second, the rest is calculated and not recorded. Anything else the developer can figure out easily or just port from script.
Opening the exe in a text editor will look like an exe most likely, unreadable.
No thanks. I'll just pull the exe, leave the bat which functionally is identical to the exe, and not pay money to avoid false detection. It's a script anyways and that's how it should live until ported to something appropriate.
If anyone wants to make their own, the Garmin fit sdk has the .jar and .BAT files, the timestamp from device is 20 years and 4 days slow, weight in grains is represented in a whole number in raw csv so idivide by 10, min, max, avg are recorded in the raw csv, speed is MM per second, the rest is calculated and not recorded. Anything else the developer can figure out easily or just port from script.