Archie Fritz

My Veracrypt boot loader used to work with the Windows boot Manager loader in my BIOS but would no longer work after installing the latest Windows 10 cumulative update KB5031445. After installing the update the Veracrypt password entry screen would no longer appear when starting up my computer but instead Windows kept trying to repair my Windows installation but failed because it obviously could not make sense of the full disk encryption on my system boot drive C:. Luckily there was another option...

Well I found this repair upgrade procedure on You Tube which says it's absolutely essential to decrypt your System C: drive before attempting the Windows repair upgrade procedure. https://www.youtube.com/watch?v=5vuaXGox5f0 I have Acronis True Image but I don't have enough confidence in it, mainly because I've never actually used it, to experiment with trying the repair upgrade procedure on an encrypted drive. I think I'll just play it safe and decrypt the system drive first as he suggests. A bit...

Do I need to or should I disable Secure Boot in my UEFI Bios prior to decrypting my fully encrypted system drive C:/ ???

I need to do a Windows repair upgrade on my system C:/ drive which is fully encrypted using Veracrypt. A Windows repair procedure reinstalls Windows but leaves my personal files and programs intact. Does anyone know if this procedure can safely be carried out without having to decrypt my system drive C:/? The procedure's description says it will need to reboot my drive several times but what I'm not sure about is whether it might rewrite my boot loader restoring the old Windows boot loader rendering...

Keepass dangerous URL warning from Bitdefender

Got the problem solved and now everything is working OK. The problem stemmed from not understanding exactly how autotype was doing it's search for the correct entry. In my case it does a matching search on two fronts. In the first case it finds a match if the complete or partial Keepass title name is contained in the webpage title. The second search method involves looking at the title name of the target webpage window added under the Auto-Type tab settings. This seems to have to match exactly but...

Autotype works perfectly in Google Chrome but when I use the Microsoft Edge browser none of my entries seem to work with autotype. Anyone know what's going on here. If they work in Chrome why wouldn't they work in Edge. I have the latest version of KeePass and both browsers

Thank you for that useful information. Exactly how does it make the match between the Window's web page title and the KeyPass title. Does it only require a single word in both to match up or are multiple words or phrases required. Is the order of the common words important? If there are words which are not in common, does this present a problem with the matching. I'm just curious as to how this matching process is implemented.