Remove Adobe CS4 Drive Context Menu Entry


Recommended Posts

Any of you who have installed Adobe CS4 will know you will get a context menu entry for Adobe CS4 Drive, even if you chose not to install the actual program so effectively the entry is useless. After some googling and experimenting found two ways to remove it.

1. Install & Uninstall

Install Adobe CS4 Drive using the installer then uninstall it. This seems to get rid of it.

2. Manual Remove

Open Regedit and delete these two entries.

HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers\{C95FFEAE-A32E-4122-A5C4-49B5BFB69795}

HKEY_CLASSES_ROOT\Directory\Background\shellex\ContextMenuHandlers\{C95FFEAE-A32E-4122-A5C4-49B5BFB69795}

Hope this helps some people.

  mail said:
Any of you who have installed Adobe CS4 will know you will get a context menu entry for Adobe CS4 Drive, even if you chose not to install the actual program so effectively the entry is useless. After some googling and experimenting found two ways to remove it.

1. Install & Uninstall

Install Adobe CS4 Drive using the installer then uninstall it. This seems to get rid of it.

2. Manual Remove

Open Regedit and delete these two entries.

HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers\{C95FFEAE-A32E-4122-A5C4-49B5BFB69795}

HKEY_CLASSES_ROOT\Directory\Background\shellex\ContextMenuHandlers\{C95FFEAE-A32E-4122-A5C4-49B5BFB69795}

Hope this helps some people.

Great! Thank; saved me a lot of research.

  • 1 month later...

This is an even easier method to get rid of the Drive menu and not have the DLL loaded:

START -> Run...

regsvr32 /u "%CommonProgramFiles%\Adobe\Adobe Drive CS4\ADFSMenu.dll"

on 64bit Windows:

START -> Run...

regsvr32 /u "%CommonProgramFiles(x86)%\Adobe\Adobe Drive CS4\ADFSMenu.dll"

Cheers,

phaelox

  phaelox said:
This is an even easier method to get rid of the Drive menu and not have the DLL loaded:

START -> Run...

regsvr32 /u "%CommonProgramFiles%\Adobe\Adobe Drive CS4\ADFSMenu.dll"

on 64bit Windows:

START -> Run...

regsvr32 /u "%CommonProgramFiles(x86)%\Adobe\Adobe Drive CS4\ADFSMenu.dll"

Cheers,

phaelox

thanks,

it also removed the entry in context menu when i click in c: or d:

  DARKFiB3R said:
I have installed Adobe CS4, but I don't have any context menu entry's for Adobe CS4 Drive.

Maybe you guys missed an option that relates to this while customising your install?

Use this one instead

regsvr32 /u "C:\Program Files\Common Files\Adobe\Adobe Drive CS4\ADFSMenu.dll"

  phaelox said:
This is an even easier method to get rid of the Drive menu and not have the DLL loaded:

START -> Run...

regsvr32 /u "%CommonProgramFiles%\Adobe\Adobe Drive CS4\ADFSMenu.dll"

on 64bit Windows:

START -> Run...

regsvr32 /u "%CommonProgramFiles(x86)%\Adobe\Adobe Drive CS4\ADFSMenu.dll"

Cheers,

phaelox

This works perfect while the regedit method does not work (on 64).

thanks

  magik said:
I really hate how it wasn't optional to unselect it during install. :no:

That's easy to fix. On the disc, navigate to the payloads folder. In there you will find two folders; AdobePhotoshop11-core and AdobePhotoshop11-core_x64.

In each of those folders you will find a file named AdobePhotoshop11-core.proxy.xml and AdobePhotoshop11-core_x64.proxy.xml.

Open AdobePhotoshop11-core.proxy.xml (make a backup first) and find the section that begins with <Dependencies>, highlight from <Dependencies> to </Dependencies> and replace with the below changes.

  &lt;Dependencies&gt;
	&lt;ProductInfo type="required"&gt;
				&lt;Family&gt;Photoshop&lt;/Family&gt;
				&lt;ProductName&gt;Adobe Photoshop CS4 Support&lt;/ProductName&gt;
			&lt;/ProductInfo&gt;
	&lt;ProductInfo type="recommended"&gt;
				&lt;Family&gt;Creative Suites&lt;/Family&gt;
				&lt;ProductName&gt;Adobe Drive CS4&lt;/ProductName&gt;
			&lt;/ProductInfo&gt;
	&lt;ProductInfo type="critical"&gt;
				&lt;Family&gt;CSXS&lt;/Family&gt;
				&lt;ProductName&gt;Creative Services Infrastructure&lt;/ProductName&gt;
			&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
			&lt;Family&gt;NonAdobePayload&lt;/Family&gt;
			&lt;ProductName&gt;AdobeAIR1.0&lt;/ProductName&gt;

		&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
			&lt;Family&gt;NonAdobePayload&lt;/Family&gt;
			&lt;ProductName&gt;AdobeAMP&lt;/ProductName&gt;

		&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeAUM&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;Adobe Bridge CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorCommonSetCMYK&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorCommonSetRGB&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorEU CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorJA CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorNA CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorPhotoshop CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CSXS&lt;/Family&gt;
		&lt;ProductName&gt;Connect&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;Core Tech&lt;/Family&gt;
		&lt;ProductName&gt;Adobe Default Language CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;MaD&lt;/Family&gt;
		&lt;ProductName&gt;DeviceCentral&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;Adobe ExtendScript Toolkit CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;Creative Suites&lt;/Family&gt;
		&lt;ProductName&gt;Adobe Extension Manager CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;Bridge&lt;/Family&gt;
		&lt;ProductName&gt;AdobeOutputModule&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;PDF Settings CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CSXS&lt;/Family&gt;
		&lt;ProductName&gt;SearchForHelp&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CSXS&lt;/Family&gt;
		&lt;ProductName&gt;Service Manager&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="critical"&gt;
		&lt;Family&gt;Creative Suites&lt;/Family&gt;
		&lt;ProductName&gt;Suite Shared Configuration CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorVideoProfilesCS CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;Creative Suites&lt;/Family&gt;
		&lt;ProductName&gt;Adobe XMP Panels CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CSXS&lt;/Family&gt;
		&lt;ProductName&gt;kuler&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="critical"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;ALM CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
	&lt;Family&gt;Shared Technology&lt;/Family&gt;
	&lt;ProductName&gt;Adobe Camera Raw&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeCMaps CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;Type Group&lt;/Family&gt;
		&lt;ProductName&gt;Common Fonts Installation&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;Adobe Linguistics CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobePDFL CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeTypeSupport CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;Adobe WinSoft Linguistics Plugin&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
  &lt;/Dependencies&gt;

Open AdobePhotoshop11-core_x64.proxy.xml (make a backup first) and find the section that begins with <Dependencies>, highlight from <Dependencies> to </Dependencies> and replace with the below changes.

  &lt;Dependencies&gt;
	&lt;ProductInfo type="required"&gt;
				&lt;Family&gt;Photoshop&lt;/Family&gt;
				&lt;ProductName&gt;Adobe Photoshop CS4 Support&lt;/ProductName&gt;
			&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
				&lt;Family&gt;Creative Suites&lt;/Family&gt;
				&lt;ProductName&gt;Adobe Drive CS4&lt;/ProductName&gt;
			&lt;/ProductInfo&gt;
	&lt;ProductInfo type="critical"&gt;
				&lt;Family&gt;CSXS&lt;/Family&gt;
				&lt;ProductName&gt;Creative Services Infrastructure&lt;/ProductName&gt;
			&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
			&lt;Family&gt;NonAdobePayload&lt;/Family&gt;
			&lt;ProductName&gt;AdobeAIR1.0&lt;/ProductName&gt;

		&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
			&lt;Family&gt;NonAdobePayload&lt;/Family&gt;
			&lt;ProductName&gt;AdobeAMP&lt;/ProductName&gt;

		&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeAUM&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;Adobe Bridge CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorCommonSetCMYK&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorCommonSetRGB&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorEU CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorJA CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorNA CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorPhotoshop CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CSXS&lt;/Family&gt;
		&lt;ProductName&gt;Connect&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;Core Tech&lt;/Family&gt;
		&lt;ProductName&gt;Adobe Default Language CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;MaD&lt;/Family&gt;
		&lt;ProductName&gt;DeviceCentral&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;Adobe ExtendScript Toolkit CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;Creative Suites&lt;/Family&gt;
		&lt;ProductName&gt;Adobe Extension Manager CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;Bridge&lt;/Family&gt;
		&lt;ProductName&gt;AdobeOutputModule&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;PDF Settings CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CSXS&lt;/Family&gt;
		&lt;ProductName&gt;SearchForHelp&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CSXS&lt;/Family&gt;
		&lt;ProductName&gt;Service Manager&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="critical"&gt;
		&lt;Family&gt;Creative Suites&lt;/Family&gt;
		&lt;ProductName&gt;Suite Shared Configuration CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeColorVideoProfilesCS CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;Creative Suites&lt;/Family&gt;
		&lt;ProductName&gt;Adobe XMP Panels CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CSXS&lt;/Family&gt;
		&lt;ProductName&gt;kuler&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="critical"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;ALM x64 CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
	&lt;Family&gt;Shared Technology&lt;/Family&gt;
	&lt;ProductName&gt;Adobe Camera Raw x64&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeCMaps x64 CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
	&lt;Family&gt;CSXS&lt;/Family&gt;
	&lt;ProductName&gt;Creative Services Infrastructure x64&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
	&lt;Family&gt;Creative Suites&lt;/Family&gt;
	&lt;ProductName&gt;Adobe Drive CS4 x64&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;Type Group&lt;/Family&gt;
		&lt;ProductName&gt;Common Fonts Installation x64&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;Adobe Linguistics CS4 x64&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobePDFL x64 CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo type="required"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;AdobeTypeSupport x64 CS4&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
	&lt;ProductInfo visible="1" type="recommended"&gt;
		&lt;Family&gt;CoreTech&lt;/Family&gt;
		&lt;ProductName&gt;Adobe WinSoft Linguistics Plugin x64&lt;/ProductName&gt;

	&lt;/ProductInfo&gt;
  &lt;/Dependencies&gt;

The next time you need to install, you will be able to uncheck most* of what you don't want or need.

* not everything that is set to recommended will be able to be unchecked.

  • 1 month later...

Unregistering the dll doesn't seem to work for me on Vista x64 or Win7 x64, as the file path specified doesn't exist. Also I have just found out if you search for {C95FFEAE-A32E-4122-A5C4-49B5BFB69795} in the registry and delete all entries it should get rid of the entry from everywhere (Y).

  • 1 month later...

This worked for me Vista Ult X64...Thanks

  phaelox said:
This is an even easier method to get rid of the Drive menu and not have the DLL loaded:

START -> Run...

regsvr32 /u "%CommonProgramFiles%\Adobe\Adobe Drive CS4\ADFSMenu.dll"

on 64bit Windows:

START -> Run...

regsvr32 /u "%CommonProgramFiles(x86)%\Adobe\Adobe Drive CS4\ADFSMenu.dll"

Cheers,

phaelox

  • 5 weeks later...
  • 2 weeks later...
  mail said:
Update for win7 RC. Unregistering the dll doesn't work you have to rename the dll or delete it.

I'm running 64bit seven rc.

I can't find the .dll anywhere. It not in either the 64 or 86 program files folders referred to. But when I enter regsvr32 /u "C:\Program Files\Common Files\Adobe\Adobe Drive CS4\ADFSMenu.dll" it says successfully unregistered but drive context menu is still present.

Any thoughts

  • 4 weeks later...
  • 1 month later...

Here is what you need to do if you have Windows 7 RC 64- bit (build 7100). None of what people have said worked for me. I realized you need to run the command prompt with administrator privileges for the changes to take effect.

1. Start > All Programs > Accessories > right click Command Prompt and select Run As Administrator

2. Type the following: regsvr32 /u "C:\Program Files\Common Files\Adobe\Adobe Drive CS4\ADFSMenu.dll"

3. Click OK and then check by right clicking on a file in a Windows Explorer window.

  • 3 months later...
  VQuick said:
Here is what you need to do if you have Windows 7 RC 64- bit (build 7100). None of what people have said worked for me. I realized you need to run the command prompt with administrator privileges for the changes to take effect.

1. Start > All Programs > Accessories > right click Command Prompt and select Run As Administrator

2. Type the following: regsvr32 /u "C:\Program Files\Common Files\Adobe\Adobe Drive CS4\ADFSMenu.dll"

3. Click OK and then check by right clicking on a file in a Windows Explorer window.

Thanks, that worked for me. I never could get it to work in Vista though, oddly. I tried everything mentioned in this thread too. That's moot now though. :yes:

  • 3 weeks later...
  wehavetogoback said:
This is the method posted by Phaelox, modified for Windows 7 beta 64-bit:

Just type in Start>Run...

regsvr32 /u "C:\Program Files\Common Files\Adobe\Adobe Drive CS4\ADFSMenu.dll"

\o/

Sorry to bump this, but wanted to say thanks. This worked for me.

Stupid Adobe.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Mobapad Huben2 review, one of the first capacitive joystick controllers to release by Robbie Khan In 2024, I was lucky enough to have had early hands on with the world's first Tunnel magnetoresistance (TMR) stick controller, the PB Tails Crush Defender. TMR promised better precision than hall-effect, better resolution and better polling rates. Both technologies use magnetism to relay the stick position with high levels of accuracy and no stick drift. Hall-effect is still the dominant technology, but TMR is fast taking its place. In the console world, first party controllers still use traditional potentiometers for the sticks, but a growing trend in the modding community has seen people replacing those sticks with TMR or hall-effect modules. These mods require soldering and calibration, so not a job for the average gamer. Since then, many other brands have released their TMR stick implementations into new controller models, my personal view, having seen what's out there now, is that TMR has matured into something quite excellent. I still game with the Defender, for example. Today I bring an early look at one of the first capacitive stick controllers to hit the market, the Huben2 by Mobapad. What is a capacitive joystick? What surprised me most about the Huben2 package was just how good everything looks and feels. I don't think photos do it justice, in the hands, the quality of the plastic and grips are all very good. There will be frequent comparisons to the GameSir Tarantula Pro here, since it has long been my personal benchmark thanks to it being an excellent all-round package with bags of customisation and very high quality construction. Let's check out the Huben2 in a bit more detail. Specifications Platforms Switch, iOS, Android, Windows, Steam Input modes Bluetooth, dongle, wired Polling rates Up to 1000Hz Sticks KSilver capacitive analogue Stick caps Removable silicone with metal necks for anti-friction Deadzones 0% Raw sensors Yes, activated via desktop/mobile app Triggers Hall-effect triggers with Omron microswitches in lockout mode D-Pad Omron mechanical switches with swappable cross/circle button face Shoulder buttons Tactile switches Accessory buttons Tactile switches ABXY buttons Omron mechanical switches Back buttons M1-M4, tactile switches Motion control 6-axis gyro control for PC and Switch Connections USB-C Macro/Turbo Yes Vibration ALPS HD Rumble RGB Power LED can be customised Construction ABS plastic Battery 1000mAh, 15 hours playtime eManual Link Release date July 2025 Price $79.99 (special offer) / £58.74 (special offer) Unboxing The packaging is quite nice, not that this matters much, but from the box to the contents inside, everything has a premium feel about the whole presentation and material quality. The protective hard shell case is very nice quality, the best I have laid hands on to date in fact, these must cost a fair bit to produce to this standard. Mobapad Huben2 carry case It's nice to see that both types of d-pad cap included, I never liked the circular cap found on other controllers, but here, with the Omron mech switches, this cap feels rather nice to the point I prefer how it operates compared to the traditional cross-type. The wireless dongle is 1000Hz and it is already paired to the controller out of the box, although manual pairing is quick and easy. The USB cable is high quality and braided, should you ever need to use it, though thankfully unlike some other controllers, the port on the controller is flush with the surface and not recessed, so any third party USB cable will work just fine. both grips have a rubberised layer that's comfortable and grippy, I am unsure as to how long these will last as in the past I have seen similar things start to peel away after a year of use: Mobapad Huben2 details gallery You may have noticed the switch toggles on the backside near each trigger. These lock the triggers into hair trigger mode which then actuates a mechanical microswitch under each trigger. Activating the lockout is easy and satisfying, but to revert back to analogue trigger mode requires quite a bit of finger force, more than I feel happy about as it requires more concentration and energy which means attention drawn away mid-gameplay. The top faceplate is swappable, though there are no alternative options to buy, yet, the included cover is double glazed with a top layer that's clear. The whole piece feels rigid and high quality again, though some may find the glossy top finish a bit annoying depending on how oily your hands get during heated gaming, because during those situations a matte textured surface offers better comfort and grip. You may have noticed that there are pogo pins on the underside of the controller, it is not clear if these are for charging or an attachment accessory as there is no documentation clarifying. We will have to wait and see what Mobapad has in store for this. Here is a video showcasing the sounds of the Omron mechanical microswitches, and let me just say, these switches are amongst the nicest feeling and sounding in combo that I have used on a controller yet. Performance & measurements I handed the pink one to my brother since he just got the Switch 2, he's pleased with the Huben2, everything seems to work fine, although it has to be said the HD Rumble is the weakest part of this controller. Whether on Switch or PC, the rumble feedback is not anywhere close to the HD Rumble rebound and depth of the motors featured on the GameSir Tarantula Pro. The Huben2's rumble feels and sounds more like a buzzing bee than nuanced haptics that can rumble low enough to satisfy the hiring action of a shotgun in Doom or Resident Evil. Even the act of running in a game feels a bit weak on the haptics front, meanwhile, the Tarantula Pro convincingly reacts to the patter of heavy running feet or jostling through rough surfaces in a game world. The capacitive sticks seem to react with precision, and the zero dead zone can really be felt in most games as even gentle touches to the stick result in movement, assuming the game being played has no developer implemented fixed-dead zones for controllers. Some games offer up the options to change this in the game settings, but most do not. I played extended sessions of GTA V Enhanced with no stick performance issues, though the trigger did prove to be a bit troublesome, more on this after the measurements... Mobapad Huben2 measurements (0% deadzone, raw sensor mode enabled) ... The triggers also come with zero dead zone out of the box, but internally the actuation doesn't register until the trigger has travelled quite a distance. This means that driving can feel a bit dead until the trigger has been pressed in further than you may be used to. Here is a GIF showing how much the trigger has to travel before the screen register an input of even 0.02% Other tests showed that whilst the capacitive sticks are largely excellent, there is processing/filtering going on when the sticks are moved very quickly or allowed to bounce back, a test I do with all controllers to check for filtering, take a look at this comparison versus the Tarantula Pro: Huben2 Tarantula Pro Notice how the indicator on the screen bounces back much slower on the Huben2, these clips were recorded on a 240Hz OLED monitor at 240fps, the final clip was slowed to 1/4x which then makes the differences clear. For the record, the Tarantula Pro has no noticeable filtering in in real-time, and the indicator overshoots to the opposite axis when the stick is let go, exactly as the physical stick is doing. This is something that Mobapad can fix with a firmware update, and i have passed my findings over to the team. At present, there is no way to turn off stick filtering in the apps or via button combos like you can on some other controllers. Software Configuration options are limited on the controller directly, so the phone or desktop app must be used to tweak things to preference. Mobapad's app is laid out nicely and I found no issues with connectivity, even over wireless on Windows. Here is a look at all of the tabs within it: The desktop app can be found on the Windows Store, or by searching Mobapad in your phone's app store. Conclusion The Huben2 is a good controller, its normal RRP is a little high for my liking having experienced all manner of controllers these past 18 months, but if you grab one at the discounted price, then it could be a suitable controller for you. Where it is missing some features, these could be added with a firmware update, such as button combos to disable the stick filtering which removes the latency on bounce back and snap-stick movements. Sadly, one area which I do not think can be fixed with an update is the trigger travel distance before actuation, it feels like this is part of the physical build rather than a sensor register in the controller firmware. Clarification from Mobapad is required to confirm this. The build quality is very good, the app on both mobile and desktop work well, the Omron switches sound and feel superb, and the accessories included are a welcome addition that competes the package. But package alone doesn't make a controller great, everything has to gel, and that includes features like customisation. I only have one small nitpick to make, and that is the silicone quality on the joystick caps. They are OK, but GameSir controllers have much better grip on the sticks thanks to adopting Sony's cap shape and near-identical quality of silicone. It is a shame that the Huben2 cannot remap the back buttons to keyboard buttons on PC, GameSir allows this in all recent releases from the past year, customisations are saved directly onto the controller so remaps are usable on other computers. The Huben2 only allows remapping the four back buttons to existing face buttons, and in my opinion, this is quite pointless. I never quite understood why this was so common with brands when these are PC controllers primarily. If a good discounted price is not possible, then a GameSir Cyclone 2 or later model would be a more suitable option offering more features, excellent TMR sticks which perform just as well as these capacitive sticks, and have no filtering applied to them, should this be an important deciding factor for you.
    • I had a G2 and it was a pretty good phone. I was disappointed to see LG exit the smartphone business.
    • Its a good price but the ideapads are pieces of garbage. We bought 3 for employees 2 years back. Within 6 months trackpad issues, screen issues, usb port issues and wifi issues on all machines. Lenovo's customer service basically told us with the ideapads, you are on your own and good luck. Their business computers are really good.
    • >Interestingly, the rings came off without any physical damage to the device. With a HUGE amount of effort. The video OP makes it clear he doesn't think they'd ever come off in normal use.
    • Samsung Galaxy Z Fold7 may not come with Galaxy S25 Ultra's camera rings by Sagar Naresh Bhavsar When Samsung launched the Galaxy S25 Ultra earlier this year, it remained in the news for its top-of-the-line premium features, but also for a couple of drawbacks. Firstly, it made headlines because Samsung removed the Bluetooth functionality from the S-Pen on the Galaxy S25 Ultra, removing one of the key features: taking remote pictures and videos. But then a jarring issue came to light. The Galaxy S25 Ultra drew attention for its camera rings falling off. Yes, the $1,300 phone featured thick camera rings that were simply glued on top of the cameras. Interestingly, the rings came off without any physical damage to the device. Now, some interesting details about the camera rings on the upcoming Galaxy Z Fold7 have popped up. According to reliable leaker IceUniverse, Samsung was quite keen on keeping the Galaxy S25 Ultra-like camera rings on the upcoming premium Galaxy Z Fold7. However, after facing a strong backlash, the company has supposedly decided to scrap them. In fact, the leaker added that the cheap-looking Saturn rings design was urgently removed from the Galaxy Z Fold7, and instead, the company is bringing back the cleaner look of the Galaxy Z Fold5. Recently, multiple images of the Galaxy Z Fold7 were leaked, which seemingly suggest the same. The foldable is expected to come in three colors: blue, silver, and black. This year's Galaxy Z Fold7 is expected to be much thinner and lighter as compared to last year's foldable. We are just a few days away from the official unveiling. The pre-reserve window is already open, and if you are interested, you can get $50 credit and up to $1,150 additional savings.
  • Recent Achievements

    • Reacting Well
      Gromvar earned a badge
      Reacting Well
    • Dedicated
      BreakingBenjamin earned a badge
      Dedicated
    • Week One Done
      Hartej earned a badge
      Week One Done
    • One Year In
      TsunadeMama earned a badge
      One Year In
    • Week One Done
      shaheen earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      537
    2. 2
      +FloatingFatMan
      176
    3. 3
      ATLien_0
      161
    4. 4
      Skyfrog
      107
    5. 5
      Som
      101
  • Tell a friend

    Love Neowin? Tell a friend!