Windows 10: Creating a registry patch for a deletion

I understand that by EXPORTING a key, one can create a registry patch containing the modification of THAT key, but how to create a patch for the DELETION of a key ?

:)

 

Macromedia Flash registry keys non deletable?

Hello, friends.
On friend machine I made the mistake of installing the Adobe Macromedia Flash, instead of just depacking the installer and copy over the relevant files in Firefox plugins. As result, there are several non-deletable (regeditor refuse to delete them, CCleaner did not delete them as well) registry entries:




Both from Flash 9b and 10b versions as you can see in the image. Since regedit refuse the delete the keys AND CCleaner also refuse to delete them, I tried even the Registry Booster, yet this one did not even list them as error. If that is significant, I don't know. I just want them to "go away" and don't know how.
Thinking about Windows PE boot, but not sure if that is safe and if that will allow well me to manipulate with registry... Is not there any other way? There is NOTHING from the flash files in Windows directory at all. All are removed/deleted. I stick with the
flashplayer.xpt
NPSWF32.dll
NPSWF32_FlashUtil.exe
files extracted from the install and put in Firefox / Plugins, so I will not ever install that crap again. Never did on my machine and no problemo. But in case someone do, is there a known way to fix this? Using the Adobe utility to clean up is NOT the way to do...
Also installing new version did not seems to fix a thing.

 

Create registry installation values?

Same issue exists with Blizzard games, there you just have to add the gamepath to the registry and you can patch again (no other registry entries needed)

 

Delta size too big when creating patches

I'm using WiX to create installers and patches for an application. We previously used a bdiff-based method to create patches, and are able to get comparable results in
WiX which uses Delta patching (specifically mspatchc.dll) (https://msdn.microsoft.com/en-us/library/bb417345.aspx)

However one particular file has deltas much larger than expected - from an original 100MB file, bdiff will create a
15KB patch, while Delta returns an 18MB patch.

I've raised the issue on the WiX-users mailing list, and feedback from there suggests that the issue might be in Delta itself. Is there anything I can try to reduce the patch size myself, or is this something that needs fixing?