This question is a means of preventing automated form submissions by spambots.
What are the l a s t four characters of "92843242aef63749bef45cea"? You must also add "xx!1.." to the answer but type "1" as a word not a number.
Smilies
:clap: :crazy: :thumbdown: :thumbup: :wtf: :yawn: :tired: :relaxed: :grin: :smile: :wink: :sad: :eek: :shock: :???: :cool: :lol: :mad: :razz: :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :neutral: :mrgreen: :geek: :ugeek: :eh: :lolno: :problem: :shh: :shifty: :sick: :silent: :think: :wave:
   

If you wish to attach one or more files enter the details below.

EMPTORXC, 2014-01-16 06:07 »

MasterOne Glad you got it fixed.
Elsewhere, others have got around this problem by running a particular program
(including ccc.exe) in '[earlier operating system] compatability mode'.

MasterOne, 2014-01-14 06:21 »

Non Hic wrote:I disable that junk as soon as I see it. I hate that thing. Nvidia has similar junk services running in background as well. I always kill those.


I can't because I have to knock up scaling to 0% in CCC, so it doesn't look like my desktop is in a picture frame on my LCD monitor. On Linux with the X.org driver, it scales correctly, right out of the box.

Non Hic wrote:I second that. Their repair tools are shit. Their support forums are shit and the support staff are most of the time clueless.


Good thing there are alternatives to Windows. :)

!, 2014-01-06 01:34 »

MasterOne wrote:...Catalyst Control Center rely on .NET...

I disable that junk as soon as I see it. I hate that thing. Nvidia has similar junk services running in background as well. I always kill those.

MasterOne wrote:...Fuck Microsoft and their crappy software. Their repair tool couldn't handle that? :lol:

I second that. Their repair tools are shit. Their support forums are shit and the support staff are most of the time clueless.

MasterOne, 2014-01-04 21:57 »

Well, I solved my own problem by adding the key manually. Here are the instructions if it happens to anyone else:

1. Open Regedit
2. Navigate to: HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFramework
3. Right click in the right pane, and select: "New > String Value"
4. Name it: "InstallRoot"
5. Point it to the .NET Framework installation directory. On my system, it's: "C:WindowsMicrosoft.NETFramework64"

Windows works the best when you don't touch or install a thing. Fuck Microsoft and their crappy software. Their repair tool couldn't handle that? :lol:

.NET Framework Woes

MasterOne, 2014-01-04 21:10 »

I'm having trouble getting .NET 4.51 to work after updating my PC's AMD graphics drivers. One of the stupid things AMD did is make the Catalyst Control Center rely on .NET (which runs like molasses), and when .NET doesn't work due to whatever error the user is getting, they are possibly shit out of luck as many users end up having to completely reinstall Windows. I get this error: ".Net Framework Initialization Error" "Please set registry key HKLMSoftwareMicrosoft.NETFrameworkInstallRoot to point to the .Net Framework install location"

Untitled.jpg
Untitled.jpg (27.79 KiB) Viewed 13696 times


I have tried uninstalling and reinstalling .NET numerous times, running the .NET repair tool, and the .NET Framework Cleanup Tool, all which haven't done shit. The fucking thing still won't work. I then ran the .NET verification tool and it fails verification. Here's a snippet from the end of the log file where it shows some important stuff:

Code: Select all

[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFrameworkpolicystandardsv1.0.0
   Value: v4.0.30319
   Expected Data:   30319
   Actual Data:   30319
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFrameworkpolicystandardsStandard CLI 2002
   Value: v4.0.30319
   Expected Data:   4095
   Actual Data:   4095
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFrameworkpolicystandardsStandard CLI 2005
   Value: v4.0.30319
   Expected Data:   4095
   Actual Data:   4095
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFrameworkpolicyupgrades
   Value: 4.0.30319
   Expected Data:   4.0.0-4.0.30319
   Actual Data:   4.0.0-4.0.30319
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFrameworkpolicyv4.0
   Value: 30319
   Expected Data:   30319-30319
   Actual Data:   30319-30319
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Client
   Value: Install
   Expected Data:   1
   Actual Data:   1
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Client
   Value: InstallPath
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Client
   Value: Servicing
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Client
   Value: TargetVersion
   Expected Data:   4.0.0
   Actual Data:   4.0.0
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Client
   Value: Version
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Client (Common)] - stop parsing entries
[01/04/14,11:52:14] Not running action 'Registry - .NET Framework 4 Client (32-bit)' for product '.NET Framework 4.5.1' because the OS condition does not match
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Client (64-bit)] - start parsing entries
[01/04/14,11:52:14] ***WARNING*** Key: HKLMSOFTWAREMicrosoft.NETFramework
   Value: InstallRoot
   Expected Data:   C:WindowsMicrosoft.NETFramework64   Actual Data:   NOT FOUND
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Client (64-bit)] - stop parsing entries
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Client (Wow6432Node)] - start parsing entries
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFramework
   Value: InstallRoot
   Expected Data:   c:windowsmicrosoft.netframework   Actual Data:   c:windowsmicrosoft.netframework[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFrameworkpolicystandardsv1.0.0
   Value: v4.0.30319
   Expected Data:   30319
   Actual Data:   30319
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFrameworkpolicystandardsStandard CLI 2002
   Value: v4.0.30319
   Expected Data:   4095
   Actual Data:   4095
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFrameworkpolicystandardsStandard CLI 2005
   Value: v4.0.30319
   Expected Data:   4095
   Actual Data:   4095
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFrameworkpolicyupgrades
   Value: 4.0.30319
   Expected Data:   4.0.0-4.0.30319
   Actual Data:   4.0.0-4.0.30319
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoft.NETFrameworkpolicyv4.0
   Value: 30319
   Expected Data:   30319-30319
   Actual Data:   30319-30319
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Client
   Value: Install
   Expected Data:   1
   Actual Data:   1
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Client
   Value: InstallPath
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Client
   Value: Servicing
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Client
   Value: TargetVersion
   Expected Data:   4.0.0
   Actual Data:   4.0.0
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Client
   Value: Version
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Client (Wow6432Node)] - stop parsing entries
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Full (Common)] - start parsing entries
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: Install
   Expected Data:   1
   Actual Data:   1
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: InstallPath
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: Servicing
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: TargetVersion
   Expected Data:   4.0.0
   Actual Data:   4.0.0
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: Version
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Full (Common)] - stop parsing entries
[01/04/14,11:52:14] Not running action 'Registry - .NET Framework 4 Full (32-bit)' for product '.NET Framework 4.5.1' because the OS condition does not match
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Full (64-bit)] - start parsing entries
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Full (64-bit)] - stop parsing entries
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Full (Wow6432Node)] - start parsing entries
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: Install
   Expected Data:   1
   Actual Data:   1
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: InstallPath
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: Servicing
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: TargetVersion
   Expected Data:   4.0.0
   Actual Data:   4.0.0
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: Version
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Section [Registry - .NET Framework 4 Full (Wow6432Node)] - stop parsing entries
[01/04/14,11:52:14] Not running action 'Registry - .NET Framework 4.5 (32-bit)' for product '.NET Framework 4.5.1' because the OS condition does not match
[01/04/14,11:52:14] Section [Registry - .NET Framework 4.5 (64-bit)] - start parsing entries
[01/04/14,11:52:14] Section [Registry - .NET Framework 4.5 (64-bit)] - stop parsing entries
[01/04/14,11:52:14] Section [Registry - .NET Framework 4.5 (Wow6432Node)] - start parsing entries
[01/04/14,11:52:14] Key: HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4Full
   Value: Release
   Actual Data:   REGISTRY VALUE FOUND
[01/04/14,11:52:14] Section [Registry - .NET Framework 4.5 (Wow6432Node)] - stop parsing entries
[01/04/14,11:52:14] Processing custom action 'Custom Action - .NET Framework 4.0 test application'
[01/04/14,11:52:14] ExecutablePath = 'Netfx40TestApplication.exe'
[01/04/14,11:52:14] FriendlyName = '.NET Framework 4 test application'
[01/04/14,11:52:14] TimeoutSeconds = '300'
[01/04/14,11:52:14] WaitOnExit = 'true'
[01/04/14,11:52:14] Silent = 'true'
[01/04/14,11:52:14] Launching process 'Netfx40TestApplication.exe' now
[01/04/14,11:52:14] Process successfully launched. Waiting 300 seconds for it to complete.
[01/04/14,11:52:14] ****ERROR**** Process 'Netfx40TestApplication.exe' exited with return code -2146232574
[01/04/14,11:52:14] ****ERROR**** Verification failed for product .NET Framework 4.5.1


I can't believe with all that relies on .NET, that Microsoft still can't get it stable. Yeah, it works for most people most of the time, but when you start having trouble with one of MS's bloated piles of shit software products which writes thousands of entries to the registry, one or two keys that get corrupted send the whole thing in a downward spiral. Since I have done pretty much everything short of manually adding keys back to the registry, I wanted to see if anyone here has any advice. This is exactly why I hate Windows.

Top