chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes


I am trying to convert our TFS build process to use the Auto Deploy capability described in the documenation. I believe I have configured everything correctly. However when the build gets to registering and running typemock, I am getting some errors/warnings in the log and all of the tests fail becuase type mock is not running properly.  The autodeploy path seems to be resolving correctly, it just appears to be an issue with registry access. Here is the typemock relevant ouput from the log.


Execute TypeMockRegister, Version=

Source AutoDeploy location is '$/Blah.Retail/Dependencies/Typemock/AutoDeploy'

AutoDeploy translated to 'C:Builds2Blah.RetailRetail.API.Dev-SharedSourcesDependenciesTypemockAutoDeploy'

TypeMockRegister, Company='Blah', License=’BlahLicense’, AutoDeploy=True, DeployRootDirectory=C:Builds2Blah.RetailRetail.API.Dev-SharedSourcesDependenciesTypemockAutoDeploy

Access to the registry key 'HKEY_LOCAL_MACHINESOFTWAREWow6432NodeTypeMock' is denied.

at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str) at Microsoft.Win32.RegistryKey.CreateSubKeyInternal(String subkey, RegistryKeyPermissionCheck permissionCheck, Object registrySecurityObj, RegistryOptions registryOptions) at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck) at Configuration.RegistryAccess.CreateSubKey(RegistryKey reg, String subkey) at Typemock.Common.Configuration.Core.RegistryManager.CreateTypemockKey(RegistryKey rootKey) at Typemock.Common.Configuration.Core.RegistryManager.CreateTypemockKey() at TypeMock.CLI.Common.TypeMockRegisterInfo.Execute() at TypeMock.TFS.TypeMockCodeActivityBase.Execute(CodeActivityContext context)


Execute TypeMockStart, Version=

TypeMocktart: Target = , ProfilerLaunchedFirst = False, Link = , LogLevel = 0, LogPath = , DisableAutoLink = False

The registryenvironment values of Typemock Isolator seemes to be corrupt, please try re-installing Isolator.

at TypeMock.Configuration.Core.GetInstallDir() at TypeMock.CLI.Common.TypeMockStartInfo.Execute() at TypeMock.TFS.TypeMockStart.ExecuteInternal() at TypeMock.TFS.TypeMockCodeActivityBase.Execute(CodeActivityContext context)

Any help in resolving this issue would be greatly appreciated. 



asked by juice_johnson (9.8k points)
edited by juice_johnson

1 Answer

0 votes



It seems that the build process is does not run with elevated privileges, which means that it doesn't have access to the registry to perform the register task needed for automatic deployment.

"Access to the registry key 'HKEY_LOCAL_MACHINESOFTWAREWow6432NodeTypeMock' is denied."

Running the build as administrator should fix this.



We released Isolator 8.3 on

answered by alex (17k points)