oiliop.blogg.se

1. Visual studio 2010 shell invalid license data install#
2. Visual studio 2010 shell invalid license data full#
3. Visual studio 2010 shell invalid license data trial#

Visual studio 2010 shell invalid license data install#

This specific issue is most likely to be encountered by someone with a "virgin" install of Windows since it is not so difficult to set the clock incorrectly when setting up a new computer and then fix it later (and if you fix the clock hours after installing the product, it might be hard to put it all together and realize what happened).īackground: Visual Studio 2012 Pro installed by Administrator account.Īs "Joe User" (member of Win 7 Users group, but NOT Adminstrators) I got the error message. The next day, I was able to set the clock back to the correct date and continue using the product.īased on other answers to this question, it would appear there are numerous reasons that you could receive this message. In my case, the resolution was quite simple - set the clock back ahead to the wrong date.

Visual studio 2010 shell invalid license data trial#

I have had this EXACT problem with VS2010 Professional Trial / Evaluation download. Re-installing Windows is an almost certain fix, but also an extremely drastic one.

I don't have the definitive fix for this so far, as I cannot adequately edit the permissions for the affected registry keys. On my affected system the owner cannot be displayed and no permissions are shown when viewed by admin.

Visual studio 2010 shell invalid license data full#

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Licenses and subkeys needs to be owned by SYSTEM with admins having full access. I believe that the problem is in fact corrupt permissions/ownership of registry keys.

It simply assumes a corrupt installation source. Since this is virtually a virgin Win7 install, the only conclusion is that MS have broken their licesing checks again (why check for a license on a free product?).Įdit: Following further investigation I have concluded that the advice given by Microsoft is useless and does not attempt to diagnose the problem.

To say it's frustrating is an understatement and the disinterest from Microsoft in fixing what appears to be a common problem (you can find lots of search engine 'hits' for the problem, none for a solution) is quite unbelievable. Have tried everything suggested by the Microsoft people, including uninstalling, cleaning up, reinstalling both from the web installer and the VS2010 Express iso - with the same result every time. I have the same problem with Windows 7 Pro.