The way to remove the automation of Java in Windows

Somewhere in six months or a year ago, I helped a man with a problem: he wanted to automatically remove anything that belongs to the Java, a computer running Windows.
First, I looked, whether the race game installer some key that will do it.
I do not remember exactly, I think still found it, but the functionality was broken, the installer does not perform the desired function.
Additional options I google sorts VB-solutions, or require .NET, how JavaRa.
In the end I came up for discussion, which found a treasured place with useful command wmic, and eventually degenerated into a solution in a very small batch file that uses only the means of the system to fulfill the purpose for which the longest written scripts.
The team is part of WMI, a tamed present in Windows 2000 and above.
I think a little explanation can not hurt:
The first part removes all installation, starting with «Java» (Java 6 and above), the second part – «J2SE» (Java 5).
I do not remember whether it copes with Java 4, but I do not think that would be a problem to modify the batch file.
In each of the forms file% TEMP% deleteAllJava_1.txt, there will be lines with product identifiers. Then use the findstr eliminated only the IDs, the excess is removed. The result is the file% TEMP% deleteAllJava_2.txt, and the first is removed. Next, using the brute force for the lines from the second file is run the command to remove the product by ID (msiexec key / x).
Plus, run the batch file should be performed with administrator rights, then the UAC request will be made only once at startup rather than every time you uninstall the package.
It is worth noting that if even some application will start with Java words or the J2SE, it also gets under the knife, so I will appreciate if you tell us how to fix this is a script that he did not break the wood.

How to completely remove and then reinstall Skype for Windows?

To get started, try removing and reinstalling the usual a Skype, to see if this fixes the problem.
Before uninstalling, we recommend that you create a backup copy of the history file Skype, so you can restore it later.
To remove and then reinstall a Skype, do the following:

  1. Quit Skype and make sure the program is closed.
  2. To do this, on the keyboard, press Windows and R key to open the “Run”.
  3. Type appwiz.cpl, and click “OK”.
  4. In the list that appears find Skype, click the item, right-click and select Delete.

    Note. If you can not find Skype in the list of installed programs, follow these instructions.

  5. Download and install the latest version of Skype.

 

If, after simply removing and reinstalling the problem persists, you can completely remove and then reinstall Skype for Windows desktop by following the instructions below. Please note that a complete removal of Skype as account settings and chat history can be deleted.
After reinstalling Skype settings of your firewall may be irrelevant. This can affect the voice quality. To avoid this, you can update your firewall settings.

How to uninstall Internet Explorer

The following instructions apply to both the operating system Windows 7 and to Windows Vista.

1. Click the Start button Picture of the “Start” button in the search field, enter a phrase and the program components, and then in the left pane, click View installed updates.
2. In section Remove updates, go to Microsoft Windows.
3. Click Windows Internet Explorer, right-click 9, click Uninstall, and then click Yes when prompted.

Press one of the buttons below:

- Restart now (to finish the removal of Internet Explorer 9 and restore a previous version of Internet Explorer process).
- Restart later

Cleaning the Context Menu by Hacking the Registry

If you want to clean things up the truly geeky way, you can open up regedit.exe through the start menu search or run box, and then browse down to one of the following keys… sadly the context menu items are not stored in a single location.

Most of the menu items that used for all files and folders can be found by looking at one of these keys:

HKEY_CLASSES_ROOT\*\shell

HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers

HKEY_CLASSES_ROOT\AllFileSystemObjects\ShellEx

Items that are specific to folders can usually be found in one of these keys instead:

HKEY_CLASSES_ROOT\Directory\shell

HKEY_CLASSES_ROOT\Directory\shellex\ContextMenuHandlers

How to Clean Up Your Messy Windows Context Menu

Instead of hacking the registry, you can use two different NirSoft utilities to clean up the context menu. Sadly, some of the menu items are implemented as Explorer shell extensions (like the “shellex” keys we explained above), and some are implemented as regular context menu items (like the regular “shell” keys we explained above).

The first tool we will check out is ShellMenuView, which allows us to manage all of those “shell” key items with an easy to use interface.

Just browse down until you find the offending item, then click the Disable button… which will actually create a LegacyDisable key just like we explained in the manual section above.

Only allow approved Shell extensions

User Configuration\Administrative Templates\Windows Components\Windows Explorer

Description

Directs Windows to start only the user interface extensions that the system security or the user have approved.

When the system detects that the user is downloading an external program that runs as part of the Windows user interface, the system searches for a digital certificate or requests that the user approve the action. If you enable this policy, Windows only starts approved programs.

This policy is designed to protect the system from damage from programs that do not operate correctly or are intended to cause harm.

Tip-icon Tip

To view the approved user interface extensions for a system, start a registry editor (Regedt32 or Regedit). The system stores entries representing approved user interface extensions on a system in the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved.

How to list Explorer extensions and disable them?

Use  Autoruns from Sysinternals (Microsoft).

This utility, which has the most comprehensive knowledge of auto-starting locations of any startup monitor, shows you what programs are configured to run during system bootup or login, and when you start various built-in Windows applications like Internet Explorer, Explorer and media players. These programs and drivers include ones in your startup folder, Run, RunOnce, and other Registry keys. Autoruns reports Explorer shell extensions, toolbars, browser helper objects, Winlogon notifications, auto-start services, and much more. Autoruns goes way beyond other autostart utilities.

Autoruns‘ Hide Signed Microsoft Entries option helps you to zoom in on third-party auto-starting images that have been added to your system and it has support for looking at the auto-starting images configured for other accounts configured on a system. Also included in the download package is a command-line equivalent that can output in CSV format, Autorunsc.

You’ll probably be surprised at how many executables are launched automatically!

Screenshot

Autoruns

Usage

Simply run Autoruns and it shows you the currently configured auto-start applications as well as the full list of Registry and file system locations available for auto-start configuration. Autostart locations displayed by Autoruns include logon entries, Explorer add-ons, Internet Explorer add-ons including Browser Helper Objects (BHOs), Appinit DLLs, image hijacks, boot execute images, Winlogon notification DLLs, Windows Services and Winsock Layered Service Providers, media codecs, and more. Switch tabs to view autostarts from different categories.

To view the properties of an executable configured to run automatically, select it and use the Properties menu item or toolbar button. If Process Explorer is running and there is an active process executing the selected executable then the Process Explorer menu item in the Entry menu will open the process properties dialog box for the process executing the selected image.

Navigate to the Registry or file system location displayed or the configuration of an auto-start item by selecting the item and using the Jump to Entry menu item or toolbar button, and navigate to the location of an autostart image.

To disable an auto-start entry uncheck its check box. To delete an auto-start configuration entry use the Delete menu item or toolbar button.

The Options menu includes several display filtering options, such as only showing non-Windows entries, as well as access to a scan options dialog from where you can enable signature verification and Virus Total hash and file submission.

How to install Windows Extension

A Shell extension handler object must be registered before the Shell can use it. This topic is a general discussion of how to register a Shell extension handler.

Any time you create or change a Shell extension handler, it is important to notify the system that you have made a change. Do so by calling SHChangeNotify, specifying the SHCNE_ASSOCCHANGED event. If you do not call SHChangeNotify, the change might not be recognized until the system is rebooted.

There are some additional factors that apply to Windows 2000 systems.

As with all Component Object Model (COM) objects, you must create a GUID for the handler using a tool such as Guidgen.exe, which is provided with the Windows Software Development Kit (SDK). Create a subkey under HKEY_CLASSES_ROOT\CLSID whose name is the string form of that GUID. Because Shell extension handlers are in-process servers, you also must create an InprocServer32 subkey under that GUID subkey with the (Default) value set to the path of the handler’s DLL. Use the apartment threading model. An example is shown here:

 

HKEY_CLASSES_ROOT
   CLSID
      {00021500-0000-0000-C000-000000000046}
         InprocServer32
            (Default) = %windir%\System32\Example.dll
            ThreadingModel = Apartment

Any time the Shell takes an action that can involve a Shell extension handler, it checks the appropriate registry subkey. The subkey under which an extension handler is registered controls when it will be called. For instance, it is a common practice to have a shortcut menu handler called when the Shell displays a shortcut menu for a member of a file type. In this case, the handler must be registered under the file type’s ProgID subkey.

 

Errors with Windows Installer

Quite a common problem among users of Windows all versions – msi error while installing software from a file with the extension .msi. In this article I will describe common problems with Windows Installer 7 / XP and variants of their solution, as well as make videos on current issues.

Files with the extension .msi installation packages are common (distributions) of which is placed the program. Unlike conventional «setup.exe», to run the msi file system uses the Windows Installer service (msiexec.exe process). In simple words, Windows Installer starts and unzip the files from the distribution. When the Windows Installer does not work there are a variety of errors.

Actually, I was terribly annoying, because after a stupid error message does not understand what to do next. Microsoft developed specifically for the Windows Installer Setup program expansion opportunities (mainly for system administrators), but have not taken care of properly operation of the service, or at least an adequate communications problems. And are we going to dig it :)

The problems may be with the service or may occur in the process of installing programs, when everything is set up, in principle, correct. In the first case, you need to pick the service installer, and in the second to solve the problem to a specific file. Consider both options, but first second.

Very often errors occur due to insufficient system permissions on files or folders. We can not say that the Windows Installer does not work in this case, simply add the desired right and everything is working. Just yesterday, I was faced with the fact that the distribution of the downloaded .msi did not want to be installed. At the same time successfully run the installation wizard, select a parameter, but then the system thinks a few seconds and gives an error:

Error reading from file Error 1305

«Error reading from file« filename »verify that the file exists and that you can access it» (Error 1305). Error reading from file … check whether a file exists and whether you have access to it.” Naturally, the “Repeat” button does not work, stop and cancel the entire installation. Post special meaning and can not be held, because sure the file exists and I have access to it.

Uninstall apps without Add/Remove or an uninstall program in Windows95/98

If you want to uninstall an appliction that has no uninstall program and it is not listed in the Add/Remove applet of Control Panel (or that uninstall doesn’t work), then just delete the directory/files. Drill down:

HKEY_LOCAL_MACHINE\SOFTWARE\ andHKEY_CURRENT_USER\SOFTWARE

locating the applications entry and delete them.

Use Explorer to to remove the entries from the Start Menu in either %windir%\Profiles\All Users\Start Menu\Programs\ and/or %windir%\Profiles\YourId\Start Menu\Programs\

If there is an entry in the Add/Remove list, edit:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

locate the entry and delete it. If the app has a service, edit:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services

and scroll down till you locate it. Then delete it.

If this app starts automatically and there is no entry in the StartUp folder(s), then use Regedt32 to edit:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows

load REG_SZ and
run REG_SZ

Remove the offending value and reboot.