sysprogs/WinCDEmu

Issues/Bug on the portable version

ThunderWCD opened this issue · 6 comments

ThunderWCD commented

Since on the forum the post was ignored or something similar, i'll post everything here:

  1. WinCDEmu "portable" leave trace on the registry
    How to reproduce:
    a) Use a software for making a registry compare like Regshot, better on clean machine or VM
    b) Start WinCDEMU Portable and install the driver
    c) Mount an image < -- Important, i have Mount an ISO
    d) Unmount-Uninstall the driver
    e) Compare previous-after registry key with Regshot
    Results are:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BazisPortableCDBus
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BazisPortableCDBus
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_BAZISPORTABLECDBUS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_BAZISPORTABLECDBUS

Example image:
http://i62.tinypic.com/2myykj7.png

.......................................

  1. The command line output, always of the portable version, is on the wrong line for EVERY command. is not only that line ( The driver is already installed ) but every output is in a wrong position
    Example image:
    http://i59.tinypic.com/vnnfyq.jpg

So instead of:

C:\>PortableWinCDEmu-4.0.exe /install
C:\>The driver is already installed

Needs to be:

C:\>PortableWinCDEmu-4.0.exe /install
The driver is already installed
C:\>
GnstheGrain commented

Thanks for this !

DjDiabolik commented

And on Windows 10 the drivers it's not be uninstalled!! I obtain every time "Access Denied" when try to uninstall it.

How i can fix this ?

It's can be run /uninstall from promt of dos ?

RoyiAvital commented

Any chance you update the PortableApps version (https://portableapps.com/apps/utilities/wincdemu-portable)?

Seikilos commented

And on Windows 10 the drivers it's not be uninstalled!! I obtain every time "Access Denied" when try to uninstall it.

How i can fix this ?

It's can be run /uninstall from promt of dos ?

I know this is 2 years old but if you get access denied it is because some other software is accessing the services (I forgot the details).
Sysinternals ProcExp which is a replacement for taskmanager will cause this error when it is running during the uninstall process. There may be various other processing causing the same behaviour.

  • 👍1
sskras commented

@Seikilos wrote:

I know this is 2 years old but if you get access denied it is because some other software is accessing the services (I forgot the details).

Did you debug this in the past or just read some analysis of it?

Seikilos commented

@Seikilos wrote:

I know this is 2 years old but if you get access denied it is because some other software is accessing the services (I forgot the details).

Did you debug this in the past or just read some analysis of it?

I remembered the very same issue I had while I was regularly upgrading a software on a production windows server where I replaced task manager with process explorer. It would always install the software but then fail at the end during deletion of the service that was responsible to start the software.
I analysed it back then and issuing a deletion of a services seemed to be queued somewhere and executed only after no application is accessing parts of the service "infrastructure". So a reboot would cause the service to be deleted but of course not reinstalled.

So when this happened here I checked Event Viewer System log and it stated that it tried to register a virtual driver, which worked. Since uninstalling failed (but had no trace in the logs for uninstalling it) I inferred the same issue. Then I tried the command line version and calling /uninstall told me that the uninstall was queued and not directly executed.
Since I had the same experience before, I exited proc exp and retried the /uninstall and it removed the service directly, yay.

Now all those registry entries regarding "bazis" were still there, which is odd and it was quite tricky to delete them. Even as admin I had no permission to delete those nodes manually, not even after owning them.
So I had to use another sysinternals tool to call regedit in a separate console session psexec -i -d -s c:\windows\regedit.exe
and proceeded to delete those keys. Let's say this experience was less than optimal...

  • 👍1