Error with ReleaseEngineer

From VuzeWiki
Jump to: navigation, search

When you open torrents in Windows Vista or Windows 7, you may receive error messages that "error: failed to create directory" and the displayed path may show 'releaseengineer' and/or 'macrovision'. The error may also surface related to reading/writing Vuze's settings.

Check Vuze's error logs (in 'logs' subdirectory in Configuration directory and see if they contain the text "ReleaseEngineer" in style of C:\Documents and Settings\ReleaseEngineer.MACROVISION\Application Data\Azureus\azureus.config.saving (The system cannot find the path specified)

The key part there is the part regarding "ReleaseEngineer.MACROVISION" (or "ReleaseEngineer.<SomethingElse>"). The path also starts wrongly, as in Vista/Windows7 the user profile path starts with C:\Users\<your username>\AppData ... , not with "Documents and Settings".

The reason for the error is most likely some 3rd-party DRM / copy protection tool in some old game, which is not fully compatible with Windows Vista and 7, and has messed up your Windows user profile to some extent. It has changed certain strings in Windows registry, and programs (including Vuze) get wrong information from there. Think if you have recently installed copy-protected music and/or games.

This has been discussed both in Vuze forums and in some other places:

Note: similar errors where some program has messed up Windows registry, may manifest themselves also with other error messages. One example: "Plugin bootstrap: initialization error for c:\windows\system32\config\systemprofile\AppData\Roaming\Azureus\Plugins\aefeatman_v\ (The system cannot find the path specified)"..... In the example, Vuze complains that can't set the plugin properties. The key part is to notice that it does not try your own user account's path, but in this case some general system profile's, which is wrong. Discussion:

Possible fixes[edit]

The main fix is to edit registry to contain correct information. Alternative fix is to create a new Windows user account after removing the culprit software.

Set correct values to Windows registry[edit]

Open registry editor and check the following values. <user> should be replaced with your Windows username:

Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders 
and make sure that the key "AppData" is set to "C:\Users\<user>\AppData\Roaming"
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders 
and check that the key "AppData" is set to "%USERPROFILE%\AppData\Roaming"
Computer\HKEY_CURRENT_USER\Volatile Environment 
also here the key "AppData" should be "C:\Users\<user>\AppData\Roaming"

Most likely at least some of those have been replaced by that ReleaseEngineer string. There may be also other occurences "ReleaseEngineer". You should check the registry for that.

Create new user profile[edit]

If you feel uncomfortable editing registry, one way to circumvent the problem is to create a new user account in your Windows. Based on the current information, the problem is user-specific.

If you create a new user account and start using it, you can circumvent the problem. Before creating the new account, you should probably delete the culprit software.