- This topic has 11 replies, 5 voices, and was last updated 12 years, 11 months ago by
.
-
Posts
-
I ran the program through InCtrl5 and the uninstaller (after the boot which isn’t officially requested but is needed) is very partial. Here are the things that get left behind forever:
name=WinCDEmu-3.0 **** reg list - start **** HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.ccd HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.cue HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.img HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.isoOpenWithProgids HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.mds HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.nrg HKCR.ccd HKCR.cue HKCR.img HKCR.iso HKCR.mds HKCR.nrg HKCRBazisVirtualCD.Ccd HKCRBazisVirtualCD.Cue HKCRBazisVirtualCD.Img HKCRBazisVirtualCD.Iso HKCRBazisVirtualCD.Mds HKCRBazisVirtualCD.Nrg HKLMSOFTWARESysProgs HKLMSYSTEMCurrentControlSetControlClass{4D36E965-E325-11CE-BFC1-08002BE10318} 001 HKLMSYSTEMCurrentControlSetControlCriticalDeviceDatabaseroot#bazisvirtualcdbus HKLMSYSTEMCurrentControlSetControlDeviceClasses{53f56308-b6bf-11d0-94f2-00a0c91efb8b}##?#BazisVirtualCDBus#StandardDevice#Random_DVD_iso#{53f56308-b6bf-11d0-94f2-00a0c91efb8b} HKLMSYSTEMCurrentControlSetControlDeviceClasses{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}##?#BazisVirtualCDBus#StandardDevice#Random_DVD_iso#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} HKLMSYSTEMCurrentControlSetControlDeviceClasses{6e1ec3ac-d9cc-423e-8862-bade124324c8} HKLMSYSTEMCurrentControlSetEnumBazisVirtualCDBus HKLMSYSTEMCurrentControlSetEnumRootLEGACY_UDFS HKLMSYSTEMCurrentControlSetServicesBazisVirtualCDBus HKLMSYSTEMCurrentControlSetServicesUdfsEnum **** reg list - end **** **** folders list - start **** %ProgramFiles%WinCDEmu **** folders list - end **** **** files list - start **** %SystemRoot%infoem25.inf %SystemRoot%infoem25.PNF %SystemRoot%system32driversBazisVirtualCDBus.sys **** files list - end ****Notes:
- Random_DVD_iso is the ISO I ran through the program. If something should be deleted it’s this. That list could be endless.
- What’s left in %ProgramFiles%WinCDEmu is %ProgramFiles%WinCDEmulangfiles
- %SystemRoot%infoem25.* is of course just in my own case. The formula is %SystemRoot%infoemX.inf – the installer should store the X for the uninstaller.
BTW, this is an awesome program. I realize it isn’t portable, but please complete the uninstaller. 😛
Ok, the “langfiles” is now removed.
Regarding most of the registry traces, it’s related to Windows architecture. Every time you connect a new device (e.g. a USB FLASH stick or a virtual CD-ROM), Windows creates an entry in the registry. This behavior is normal to Windows and should not create any problems to the user.
On the other hand, if you are continuously installing/uninstalling lots of programs (especially system ones) on the same PC, rather use some commercial “precise uninstaller”, or a VM with snapshots.The purpose of the uninstaller is to remove any components potentially using system resources (e.g. the driver) and the files occupying disk space. Forcing Vista/Win7 to purge device entries would be against its design. The registry keys describing the file extensions will be overwritten as soon as you install another image mounting tool (just reverting them to old values won’t be an option, as the user could remove the previously active tool before uninstalling WinCDEmu).
after the boot which isn’t officially requested but is needed
After the uninstaller has completed, no components are left in memory and no interference with other product installation can happen. Asking the user to restart just to have the last files removed “here and now” (provided that they do not interfere with anything) would be unreasonable.
@bazis wrote:
just reverting them to old values won’t be an option.
Nor should it be. What should be done is deleting those keys and, like you said, other programs in the future could re-register them.
Asking the user to restart just to have the last files removed “here and now”…would be unreasonable.
But you control the message. You can write something like “a restart is needed but only to remove some leftovers. You can continue working safely without an immediiate restart. Do you still wish to restart right now? Yes/No” (you can even put the default on “no”).
The new portable version leaves leftovers too. Here’s a reg file to delete them:
Windows Registry Editor Version 5.00 [-HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlClass{4D36E965-E325-11CE-BFC1-08002BE10318} 003] [-HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlDeviceClasses{53f56308-b6bf-11d0-94f2-00a0c91efb8b}##?#BazisVirtualCDBus#StandardDevice#PortableVirtualCD_0000#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}] [-HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlDeviceClasses{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}##?#BazisVirtualCDBus#StandardDevice#PortableVirtualCD_0000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}] [-HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumBazisVirtualCDBusStandardDevicePortableVirtualCD_0000] [-HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootLEGACY_BAZISPORTABLECDBUS]These ‘leftovers’ is the way Windows stores the information about devices. Any USB flash drive will leave exactly the same “leftovers” in any system. I would NOT recommend deleting these keys manually, as it can damage some internal dependencies maintained by Windows.
@bazis wrote:
Any USB flash drive will leave exactly the same “leftovers” in any system.
Yes, but USB devices can be easily removed with a software like USBDeview.
I guess, you can use devcon or other Microsoft tools to cleanup drive information as well. Anyway, do such leftovers cause any real inconvenience to anyone? Windows is designed to keep history of all previously connected devices, this information does not occupy any considerable amount of your disk space or RAM and does not slow your system…
i mean really, the uninstaller should work , what reason to include one if it doesnt work
ive just tried wincdemu again in hope to be able to replace daemon tools – however it didnt correctly emulate, and i wasnt able to play BR-Disc from a virtual drive. (with daemon it worked)
so i wanted to uninstall it, and it leaves all image-files with some context menu entry which i had to remove by modifiying the registry
just giving feedback, this is one of the things i didnt like at all, or at least include an instruction how to remove ALL parts of it.
however good work, and gratulations to the signing of the driver
Currently, BluRay discs are not supported, but it’s planned in the next release.
Update: try WinCDEmu 3.6 beta 1. It has an experimental support for Blu-Ray disc imaegs.InCtrl5?? My gosh, that tool is still alive??!?
I can barely remember using it. It’s been obsoleted by tools like Total Uninstall, but the problem is that they all cost money 🙁
- You must be logged in to reply to this topic.