Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: kinaton on May 31, 2015, 04:44:41 pm
-
Thanks to everyone who has helped, sadly it made situation worse.
My drive is bitlocked. Has no errors. Refresh failed and now wont boot.
-
So the windows 8 refresh didnt work and made it worse? Have you decrypted the drive yet by any chance? You should be able to even if you cant get into windows.
http://blogs.technet.com/b/mspfe/archive/2013/04/04/computer-crash-how-to-use-manage-bde-to-recover-a-partially-decrypted-hard-drive.aspx
Shane
-
Got back in, and refresh fails at 1%. This is to do with security being changed. Is there a batch file to reset all to defaults.
God I hate winblowz so much.
Wish I hadn't start this mess. 20 bad files and now 166 with bad signatures.
-
From what I have found it isnt a file permissions problem but a possible corrupt registry, try this
https://support.microsoft.com/en-us/kb/2823223
and
http://www.thewindowsclub.com/windows-8-fails-to-boot-automatic-repair-refresh-reset-pc-fail
Basically you just rename the system hive file and the software hive file, see how that does for you, make sure to only rename them and dont delete them.
Shane
-
I have no ideas
-
No ideas for what? Are you not able to rename those files?
Also have you ran a memory test on the system yet? The problems you are having are all so random, like I said in the your other thread, I run my windows repairs on windows 8 all the time and never had this trouble, so something else is going on.
So we need to cover all the bases and make sure it isnt a hardware problem, such as a bad memory module. :wink:
Shane
-
Memory fine,
hard drive checks with no error
Unable to install updates or remove updates
Can't add feature net3.5
20 missing files / 166 not valid.
Updates that are not in update list are showing as installed when trying to reinstall.
Renaming both hives will stop refresh. You have to so reinstall, which kind of defeats the issue.
-
I am looking at the list of files and it is odd that I dont have a single one of them in my file repository. I am going to go hunt them down, have you put them in the packages folder, you can backup the folder first if you like and then try updates after a reboot. We wont need to run any repairs.
Shane
-
Give me 10mins and ill send the current lists.
-
Sounds good, I have Windows 8 x86 in vmware, a lot of updates I havent done yet, doing them now so i can get the cat and mum files. Also looked at some of the updates in your lists that are missing and grabbing them as well from https://catalog.update.microsoft.com :cheesy:
Shane
-
Thanks... Shame cant install updates :undecided:
As above, those updates it's says has already been installed, but they are not in list.
-
No problem, I am going through each file and getting its KB and then going and grabbing each one. There is a lot! So give me some time, I am still working on it and getting the files as we speak :-)
Shane
-
Tweaking.com - Windows Repair - Pre-Scan
Computer: UPSTAIRS (Windows 8.1 Pro with Media Center 6.3.9600 ) (32-bit)
Started at (01/06/2015 23:31:48)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Windows Packages Files.
Started at (01/06/2015 23:31:48)
These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 133)
C:\WINDOWS\servicing\Packages\package_10_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_10_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_11_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_11_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_12_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_12_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_13_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_13_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_14_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_14_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_15_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_15_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_16_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_16_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_17_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_17_for_KB2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_18_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_18_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_19_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_19_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_1_for_kb2958262~31bf3856ad364e35~x86~~6.3.1.2.mum
C:\WINDOWS\servicing\Packages\package_1_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_1_for_KB2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_1_for_KB3035583~31bf3856ad364e35~x86~~6.3.1.15.mum
C:\WINDOWS\servicing\Packages\Package_1_for_KB3036228~31bf3856ad364e35~x86~~6.3.1.1.mum
C:\WINDOWS\servicing\Packages\Package_1_for_KB3049508~31bf3856ad364e35~x86~~6.3.1.1.mum
C:\WINDOWS\servicing\Packages\package_20_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_20_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_21_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_21_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_22_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_22_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_23_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_23_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_24_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_24_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_25_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_25_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_26_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_26_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_27_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_27_for_KB2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_28_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_28_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_29_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_29_for_KB2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_2_for_KB2958262~31bf3856ad364e35~x86~~6.3.1.2.mum
C:\WINDOWS\servicing\Packages\package_2_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_2_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_2_for_KB3042216~31bf3856ad364e35~x86~~6.3.1.1.mum
C:\WINDOWS\servicing\Packages\Package_2_for_KB3047641~31bf3856ad364e35~x86~~6.3.1.0.mum
C:\WINDOWS\servicing\Packages\package_30_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_30_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_31_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_31_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_32_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_32_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_33_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_33_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_34_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_34_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_35_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_35_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_36_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_36_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_37_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_37_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_38_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_38_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_39_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_39_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_3_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_3_for_KB2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_40_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_40_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_41_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_41_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_42_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_42_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_43_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_43_for_KB2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_44_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_44_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_45_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_45_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_46_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_46_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_47_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_47_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_48_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_48_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_49_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_49_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_4_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_4_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_50_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_50_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_51_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_51_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_52_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_52_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_5_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_5_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_6_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_6_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_7_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_7_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_8_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_8_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_9_for_kb2966828_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_9_for_kb2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_for_KB2958262_RTM_GM~31bf3856ad364e35~x86~~6.3.1.2.mum
C:\WINDOWS\servicing\Packages\Package_for_KB2958262_RTM~31bf3856ad364e35~x86~~6.3.1.2.mum
C:\WINDOWS\servicing\Packages\Package_for_KB2958262~31bf3856ad364e35~x86~~6.3.1.2.mum
C:\WINDOWS\servicing\Packages\package_for_kb2966828_rtm_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\package_for_kb2966828_rtm_gm_bf~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_for_KB2966828_RTM_GM~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_for_KB2966828_RTM~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_for_KB2966828~31bf3856ad364e35~x86~~6.3.1.4.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3035583_RTM_GM~31bf3856ad364e35~x86~~6.3.1.15.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3035583_RTM~31bf3856ad364e35~x86~~6.3.1.15.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3035583~31bf3856ad364e35~x86~~6.3.1.15.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3036228_RTM_GM~31bf3856ad364e35~x86~~6.3.1.1.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3036228_RTM~31bf3856ad364e35~x86~~6.3.1.1.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3036228~31bf3856ad364e35~x86~~6.3.1.1.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3042216_RTM_GM~31bf3856ad364e35~x86~~6.3.1.1.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3042216_RTM~31bf3856ad364e35~x86~~6.3.1.1.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3042216~31bf3856ad364e35~x86~~6.3.1.1.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3047641_RTM_GM~31bf3856ad364e35~x86~~6.3.1.0.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3047641_RTM~31bf3856ad364e35~x86~~6.3.1.0.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3047641~31bf3856ad364e35~x86~~6.3.1.0.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3049508_RTM~31bf3856ad364e35~x86~~6.3.1.1.mum
C:\WINDOWS\servicing\Packages\Package_for_KB3049508~31bf3856ad364e35~x86~~6.3.1.1.mum
Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.
These files do not keep the repairs from working, you may still run the repairs in the program.
If you need help in replacing these files, post on the Forums at Tweaking.com for help.
Files Checked & Verified: 7,372
Done (01/06/2015 23:41:50)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Reparse Points.
Started at (01/06/2015 23:41:50)
-
Ok here we go, I was able to get all the files except just a few, these
Package_1_for_KB2889543~31bf3856ad364e35~x86~~6.3.1.0.cat
Package_1_for_KB2889543~31bf3856ad364e35~x86~~6.3.1.0.mum
Package_for_KB2889543_RTM~31bf3856ad364e35~x86~~6.3.1.0.cat
Package_for_KB2889543_RTM~31bf3856ad364e35~x86~~6.3.1.0.mum
Package_for_KB2889543~31bf3856ad364e35~x86~~6.3.1.0.cat
Package_for_KB2889543~31bf3856ad364e35~x86~~6.3.1.0.mum
Which is no longer available because it was a bad update and it was replaced
https://support.microsoft.com/en-us/kb/2889543
So that means we just need to remove those entries from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages for those files, which should only be 3 entries. So remove those from there, when you do Windows and my program will stop looking for it. Windows updates and my pre scan look at the entries there to know what files to look at.
Next I have all the other files. As you know extract the zip file and put all the files in C:\Windows\servicing\Packages overwriting any that are there. Some of the missing files had to do with a .net 3.5 update, so that might explain the trouble you had with it.
Once done you have to reboot, then try windows updates again, do worry about my pre scan yet and lets see how it goes :-)
Shane
-
Removed 3 from registery
-
OK good, thats how we can get windows to not look at old, replaced updates :-)
I updated the attached files as well :wink:
Shane
-
Do I need to take control of folder
-
If you ran my permissions repair then yes you should since the permissions would have been set back to default.
Shane
-
Okay. Trying now.
-
Okay done and rebooted
-
OK good, lets see how things go now, try a few things and see how it does. We can also do a pre- scan just to see what it finds, it might still return the mum files as being bad since we didnt add the cat files back, but I am not worried about that :-)
Shane
-
Adding feature net3.5 failed
Prescan shows 177 bad.
-
Post the pre scan log for me.
Also what does the event viewer show when trying to add .net 3.5?
Shane
-
Pre scan attached i think
Event viewer : Status 0x80070bc9
IIS-webserver package failed to turn on
This is why I got out of IT support.
-
I love the stuff :-)
Ok here is what I would like you to do next. Use this .net removal tool, run it as administrator and have it remove every single version of .net on the system.
http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx
Then once done reboot, you will get some errors about .net, you can ignore them. Then download and install .net with its offline installer
https://www.microsoft.com/en-us/download/details.aspx?id=42642
Once done reboot, I have noticed that with Windows more and more things depend on .net and if it is broken in any way all things go crazy. The only real way to fix .net is by completely removing it and installing it fresh. :wink:
Shane
-
Clean done
-
OK good, let me know how the rest of it goes.
Shane
-
Your install will not take place as .net framework 4.5.2 or later is already installed.
So much for a cleaner that don't work LMFAO
-
Odd, i always had luck with that cleaner, but I havent used it in a while. Maybe it isnt removing everything.
I had another user who had trouble getting the removal to work
http://www.tweaking.com/forums/index.php/topic,3097.msg21548.html#msg21548
Instead, after using the removal they did a repair with the installer and it fixed .net, I dont know why that did the trick but the two togeather did. I am going to go see if there is any update for that removal tool, it worked great in the past, wonder why it is having trouble.
Shane
-
Ah, thats why
Not all of the above products will appear in the UI for the .NET Framework cleanup tool on every operating system. The cleanup tool contains logic so that if it is run on an OS version that includes the .NET Framework as an OS component, it will not offer the option to clean it up. This means that running the cleanup tool on Windows XP Media Center Edition or Tablet PC Edition will not offer the option to clean up the .NET Framework 1.0, running it on Windows Server 2003 will not offer the option to clean up the .NET Framework 1.1 and running it on Windows Vista or Windows Server 2008 will not offer the option to clean up the .NET Framework 2.0 or the .NET Framework 3.0.
When choosing to remove any of the above versions of the .NET Framework, the cleanup tool will also remove any associated hotfixes and service packs. You do not need to run any separate steps to remove the service pack(s) for a version of the .NET Framework.
Any .net framework that is part of the OS it wont remove. Well crap, looks like I will need to what else I can find to remove it properly.
Shane
-
Ouch :(
-
They have another tool I havent tried yet that at least verifies the .net framework. Lets see what it says about the versions.
http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
Shane