Realvnc Uninstall

[Nu Alessio]

Itseems that there are many users who have difficulty uninstalling programs like RealVNC Server from their systems. Some experience issues during uninstallation, whereas other encounter problems after the program is removed.

There could be other causes why users may not be able to uninstall RealVNC Server. An incomplete uninstallation of a program may cause problems, which is why thorough removal of programs is recommended.

Installed init script for VNC Server in Virtual Mode daemon

Start and stop the service with:

/etc/init.d/vncserver-virtuald (startstop)

Use chkconfig to start or stop the service at boot time.

I have not been able to uninstall this Component. I have tried the ubuntu way ( -to-uninstall-real-vnc-in-ubuntu-14-04), but it did not work to install deb and use dpkg to uninstall. I cannot use rpm either.

I have not been able to uninstall this Component. I have tried the

ubuntu way

( -to-uninstall-real-vnc-in-ubuntu-14-04),

but it did not work to install deb and use dpkg to uninstall. I cannot

use rpm either.[/color]

Since you are new, the way to unofficially close a ticket its to accept a best answer, people can still contribute more for people finding it in the future, but it pulls it out of the pool of unanswered and means the OP is not still actively seeking alternative perspectives.

As it stands, the way that the OP did it, I would think that the /silent was discarded/ignored. The normal non-silent vnc uninstaller would have been invoked on the remote host expecting GUI user interaction which was not visible to the remote psexec execution. As the invisible GUI sat there without any expected user interaction, the result was the uninstall failed, or just sat there forever expected a user to confirm and never being confirmed.

Why some users fail to delete an application? One possible reason is that the app is still running so the system cannot trash it. So before uninstalling the VNC, remember to check if it is active. If so, right click on the app icon in Dock, and then choose Quit.

Most third party apps can be uninstalled by deleting it from the Applications folder. Yet, if you decide to uninstall VNC by this way and think the job could be finished perfectly, you are wrong. A clean uninstall requires you to remove all its components.

By using this tool, you could easily get rid of VNC or any other unwanted apps. Want to try this handy tool? Note that Osx Uninstaller is a paid software, which means you will need to pay for a valid license before using it to remove unwanted apps.

Warning: Emptying Trash is irrevocable, and everything in the Trash will be deleted from your Mac immediately. Before performing this act, go to check if all items in the Trash are no longer needed. If you wanna avoid any risk in this act, you can just delete the app individually in the Trash. To do so, locate and right click VNC in the Trash, choose Delete Immediately, and click Delete in the pop-up window.

Basically, this trash-to-uninstall method can be used to uninstall third party apps in all versions of macOS / Mac OS X. However, for the app that provides a dedicated uninstall tool in its folder, you are suggested to run the tool to complete the uninstall.

As we mentioned before, VNC will create and store associated files (like preferences, extensions and account profiles) in multiple system directories. Those leftovers may not do harm to your system, but if you wish to remove all the traces and reclaim occupied disk space, you can take the following steps to hunt then down.

To summarize, this tutorial offers three ways to uninstall VNC software for Mac and the search trick to locate and delete VNC-related items in hidden system folders. We hope your problems can be solved after taking the methods in this page.

I have already contacted the RealVNC support people about this and opened a support ticket with them, and they have been able to duplicate my issue. The problem is that their "connection self-test" functionality FAILS WHEN BITDEFENDER IS INSTALLED, and WORKS WHEN BITDEFENDER IS UNINSTALLED!! The mystery here is that the product itself works perfectly in its normal connection functionality. And it is only their special diagnostic "connect self-test" (designed to prove that the product is installed correctly and functioning properly) which DOES NOT WORK PROPERLY!!

They are themselves now working to try and determine what is different between VNC Server's "connection self-test" and "normal operation" which could account for any difference caused by a separate software product (no doubt by the Firewall of BitDefender), but haven't figured it out yet. However like me in trying to prove that it is BitDefender which is responsible they have also tried to FULLY DISABLE ALL FEATURES OF BITDEFENDER, using the Protection interface (i.e. deactivating every available sub-feature that can be deactivated, including Firewall, etc., ) and the problem still occurs. In other words using all the available UN-CHECK items available they STILL CANNOT TEMPORARILY FULLY DISABLE BITDEFENDER. Their VNC Server "connection self-test" will not work as long as BitDefender remains installed in any way, shape, or form, no matter how little of is presumably still left installed and operational even after un-checking all available boxes.

Once BitDefender is COMPLETELY UNINSTALLED then once again VNC Server "connection self-test" functions perfectly, clearly pointing to BitDefender as the culprit responsible for this issue. And no matter the fact that in theory the product is fully and temporarily disabled by UN-CHECKING all of the "protection" sub-features, obviously there is still some basic underlying BuitDefender functionality which remains fully active and operational and has NOT BEEN DISABLED BY ME, THE USER, which is responsible for the VNC Server "connection self-test" malfunction!

This is the same story as I've already seen with BitDefender in another case (reported here, and also through recently opened BitDefender support ticket 2019121620110002 which is still open at this moment) where BitDefender interferes with the successful installation of software product Free Commander XE and instead abends with an "access violation in module ATCUF32.DLL". Same as with the story with VNC Server, attempting to temporarily fully disable BitDefender using the Protection interface and un-checking everything, it apparently DOES NOT FULLY DISABLE BITDEFENDER COMPLETELY!! In fact something remains active in the basic BitDefender functionality regardless, which apparently is sufficient to make it responsible for this ATCUF32.DLL failure that still occurs. The only way to eliminate this failure is to FULLY AND COMPLETELY UNINSTALL BITDEFENDER!!

This is ridiculous. It should not be required that the product be uninstalled just to prove that it is BitDefender IS THE CULPRIT and IS RESPONSIBLE FOR THE 3RD-PARTY SOFTWARE PRODUCT MALFUNCTION OR FAILURE!!! Of course the problem IS IN BITDEFENDER, not the 3rd-party software product, that has now been proven in two separate issues of mine: (a) cannot install software product Free Commander XE because of the access violation in ATCUF32.DLL, and (b) cannot run the VNC Server "connection self-test" which is part of the RealVNC software product.

This is now for me the second currently active (a) actual abend failure in a BItDefender component itself, or (b) failure in a 3rd-party product caused by BitDefender being installed, which has been EXPERIMENTALLY PROVEN TO BE 100% DIRECTLY RELATED TO OR CAUSED BY BITDEFENDER BEING INSTALLED! The problems are both due to BitDefender being installed, and will only be fixed when the underlying causes in BitDefender are corrected AS THEY OBVIOUSLY SHOULD BE.

(2) BitDefender currently "breaks" the "diagnostic connection self-test" of the VNC Server product, even though the normal operation of VNC Server is unaffected. No support ticket yet opened with BitDefender support, but there IS a ticket opened with RealVNC support. They have duplicated the failure caused by BitDefender, but have so far not determined exactly what makes "connection self-test" functionally different from "normal operation" in order to account for what might be the interference resulting from BitDefender.

(5) It is impossible to fully disable BitDefender TEMPORARILY by un-checking all sub-features shown in Protection. Only by FULLY UNINSTALLING BITDEFENDER is it actually possible to 100% disable 100% of the BitDefender functionality. If the product remains installed, even un-checking all of its features leaves fully operational some residual basic underlying functionality which seems to remain fully responsible for both of my current issues.

And whatever is in BitDefender that is CAUSING BOTH OF MY 3'rd PARTY PRODUCT FAILURES NEEDS TO BE FIXED!! I need to be able to install Free Commander XE as they intended, and I need to be able to run the "diagnostic connection self-test" of VNC Server as they intended.

As it turns out I have an operational workaround for the Free commander XE install failure issue. And the "connection self-test" of VNC Server is not critical, since the product itself actually works 100% perfectly even if its built-in "connection self-test" fails. But both issues have been 100% proven to be caused by BitDefender being present in the environment, which apparently cannot be eliminated by disabling any or all of the available BitDefender Protection check-options, but only by fully uninstalling the BitDefender product completely.

I reported this problem to RealVNC back in December, same time as I reported it here. They have been attempting to determine why their connection diagnostic self-test fails, whereas ordinary normal remote connection to the exact same PC works, with BitDefender present. Presumably the BitDefender firewall is the same, but there clearly is something slightly different they must be doing in the self-test that is triggering BitDefender firewall to block self-test whereas it doesn't block anything normally.

3a8082e126