Use of the SysnativeBSODApps must have fallen off in the last year. Or maybe people just didn't want to burden me with bugfixes?
At any rate, the apps have been in an awful state since Microsoft developers decided to use build numbers higher than 11000, e.g. 14393 for the Anniversary Update (my fault for assuming 11000 would be the equivalent of Windows 11). DropBox changes to what files are public versus private also made it difficult for the apps to phone home and determine what the current version number is, resulting in the pop up always appearing and saying an update may be available on our Sysnative forums. I am currently in the process of cleaning things up on both fronts. I am also working on a fix for the installer to make it more difficult to lose files during an update install or even a change in install location (for those who download files and save them in the apps directory instead of a download directory).
At any rate, the apps have been in an awful state since Microsoft developers decided to use build numbers higher than 11000, e.g. 14393 for the Anniversary Update (my fault for assuming 11000 would be the equivalent of Windows 11). DropBox changes to what files are public versus private also made it difficult for the apps to phone home and determine what the current version number is, resulting in the pop up always appearing and saying an update may be available on our Sysnative forums. I am currently in the process of cleaning things up on both fronts. I am also working on a fix for the installer to make it more difficult to lose files during an update install or even a change in install location (for those who download files and save them in the apps directory instead of a download directory).
