Davison

What I am saying (and I could be wrong) is that I don't think end users running Windows 10+ need to install the runtime at all if you do make the switch to compiling with Visual Studio 2019. So you certainly wouldn't need to bundle anything, and moving to the latest runtime should actually simplify things. I don't think there is really any worth trying to fix the older runtime issues given that the new universal runtime is included in Windows 10+ and can also be downloaded for some older operating...

Thanks for the response. I'm not an expert with Visual Studio compiler issues either. I would be in favor of moving to require the latest version of Visual Studio runtime as any Windows 10+ environment should be able to use it without even installing a runtime. If I'm understanding things correctly Visual Studio 2015 and later use a universal runtime that is included in Windows 10. For those wanting to use GM on older (unsupported) Windows environments they can always stay with an older version (or...

@bfriesen this is still a problem as of August 2021. I don't mind if you specify that Windows users need to download a redistributable package separately, but right now the binary is entirely broken without manually modifying a manifest file. It would seem that a minor release is warranted just to fix that specific issue.

I don't really have any experience with the ddru_findbad tool (only the ddru_ntfsfindbad tool) and I haven't been trying to convert and findbad results into sector locations (it also looks like the output of ddru_ntfsfindbad must be different than ddru_findbad). So I'm afraid I can't be much help--hopefully someone else can step in and offer advice.

If your goal is simply to get a list of files that are damaged by incomplete recovery and you are having difficulty with the ddru_findbad tool, you can always fall back to a more brute force method that I used before discovering the ddrutility toolset. The basics are: 1. Mount rescued image file and create a list of hashes for every file using hashdeep 2. Use ddrescue in fill-mode to fill all non-rescued areas of the image with a character string 3. Create a new list of hashes and then diff the two...

Actually I just read the release notes more closely and did see a reference to you...

I saw a thread from a couple years ago where someone had submitted a patch to remove...

Would turning off the export capability in Keepass policies have mitigated this attack?...