P pestalent1 Contributor Joined Dec 20, 2018 Posts 42 Jan 5, 2019 #21 I did this: Unfortunately same thing happened. I rebooted and got the same error. I ran the "NetFxRepairTool.exe" got the same error. I then ran "NDP472-KB4054530-x86-x64-AllOS-ENU.exe" and chose repair, no change same error. Attachments CBS.log 785.8 KB · Views: 1
I did this: Unfortunately same thing happened. I rebooted and got the same error. I ran the "NetFxRepairTool.exe" got the same error. I then ran "NDP472-KB4054530-x86-x64-AllOS-ENU.exe" and chose repair, no change same error.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 7, 2019 #22 Use the Windows key + R to open a run command Type regedit.exe and press OK Navigate to: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer Check if following registry keys have correct values: MsiExecCA32 should end with \Windows\syswow64\msiexec.exe MsiExecCA64 should end with \Windows\system32\msiexec.exe If those are correct, then highlight one and go to Edit > Permissions and verify that SYSTEM and Administrators have Full Control and not just Read permissions Repeat for the other key If you had to make changes to the registry, restart the computer or server and try the installation again
Use the Windows key + R to open a run command Type regedit.exe and press OK Navigate to: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer Check if following registry keys have correct values: MsiExecCA32 should end with \Windows\syswow64\msiexec.exe MsiExecCA64 should end with \Windows\system32\msiexec.exe If those are correct, then highlight one and go to Edit > Permissions and verify that SYSTEM and Administrators have Full Control and not just Read permissions Repeat for the other key If you had to make changes to the registry, restart the computer or server and try the installation again
P pestalent1 Contributor Joined Dec 20, 2018 Posts 42 Jan 8, 2019 #23 I could not check permissions on: MsiExecCA32 should end with \Windows\syswow64\msiexec.exe MsiExecCA64 should end with \Windows\system32\msiexec.exe My choices were: modify, modify binary data, delete and rename I could only check permissions on "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer" itself: This seemed to meet your instructions. Did I misunderstand your directions?
I could not check permissions on: MsiExecCA32 should end with \Windows\syswow64\msiexec.exe MsiExecCA64 should end with \Windows\system32\msiexec.exe My choices were: modify, modify binary data, delete and rename I could only check permissions on "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer" itself: This seemed to meet your instructions. Did I misunderstand your directions?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 8, 2019 #24 No, you didn't. Please download the cleanup tool and run it: https://blogs.msdn.microsoft.com/astebner/2008/08/28/net-framework-cleanup-tool-users-guide/
No, you didn't. Please download the cleanup tool and run it: https://blogs.msdn.microsoft.com/astebner/2008/08/28/net-framework-cleanup-tool-users-guide/
P pestalent1 Contributor Joined Dec 20, 2018 Posts 42 Jan 9, 2019 #25 I removed them all, then reinstalled "4NDP472-KB4054531-Web.exe" after that it is still the same. The update fails the same way. Thanks
I removed them all, then reinstalled "4NDP472-KB4054531-Web.exe" after that it is still the same. The update fails the same way. Thanks
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 9, 2019 #26 Please run the following again: Using the .NET Collect Utility Download collect.exe and save to your desktop. Go ahead and run the tool The utility creates a compressed cabinet of all the needed logs to %TEMP%\vslogs.cab. Please zip/attach to this post or if too large, send using a service such as SendSpace. Please include your CBS.log as well.
Please run the following again: Using the .NET Collect Utility Download collect.exe and save to your desktop. Go ahead and run the tool The utility creates a compressed cabinet of all the needed logs to %TEMP%\vslogs.cab. Please zip/attach to this post or if too large, send using a service such as SendSpace. Please include your CBS.log as well.
P pestalent1 Contributor Joined Dec 20, 2018 Posts 42 Jan 10, 2019 #27 Here you go: Vslogs.zip (could not find vslogs.cab) https://1drv.ms/u/s!AqOO4bZtmyk5gZIiBgkrndQ1RTEUCA CBS.log https://1drv.ms/u/s!AqOO4bZtmyk5gZIm2UhkfaRZI1NqxA Thanks
Here you go: Vslogs.zip (could not find vslogs.cab) https://1drv.ms/u/s!AqOO4bZtmyk5gZIiBgkrndQ1RTEUCA CBS.log https://1drv.ms/u/s!AqOO4bZtmyk5gZIm2UhkfaRZI1NqxA Thanks
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 10, 2019 #28 Please export your whole CBS folder for me. Thanks.
P pestalent1 Contributor Joined Dec 20, 2018 Posts 42 Jan 10, 2019 #29 Here it is: https://1drv.ms/u/s!AqOO4bZtmyk5gZIgAYbSD9q6-eBdFg
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 12, 2019 #30 Is the following update installed: KB3018238
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 13, 2019 #32 FRST Registry Search 1. Click your Start button and choose Control Panel. 2. In the upper right corner ensure the View by: is set to Category. 3. Select the Programs group. 4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway. Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. 5. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 7. Copy and paste .NET Framework into the Search box and click the Search Registry button. 8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt. 9. You may close any remaining open windows now.
FRST Registry Search 1. Click your Start button and choose Control Panel. 2. In the upper right corner ensure the View by: is set to Category. 3. Select the Programs group. 4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway. Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. 5. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 7. Copy and paste .NET Framework into the Search box and click the Search Registry button. 8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt. 9. You may close any remaining open windows now.
P pestalent1 Contributor Joined Dec 20, 2018 Posts 42 Jan 13, 2019 #33 View attachment SearchReg.txt Attachments SearchReg.txt 109.6 KB · Views: 1
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 13, 2019 #34 Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download attached file and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. 6. Try updates and if any fail, attach CBS.log. Attachments Fixlist.txt 4.9 KB · Views: 4
Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download attached file and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. 6. Try updates and if any fail, attach CBS.log.
P pestalent1 Contributor Joined Dec 20, 2018 Posts 42 Jan 16, 2019 #35 I apologize for the delay. I think I followed correctly: When I "Run *FRST64* by *Right-Clicking *on the file and choosing *Run as administrator*" Pressed OK on failed to update: Not sure if the program was hung up, I let it run for awhile and finally closed it with task manager. I then rebooted and ran the update and got the same failure as earlier. View attachment CBS.log Thanks
I apologize for the delay. I think I followed correctly: When I "Run *FRST64* by *Right-Clicking *on the file and choosing *Run as administrator*" Pressed OK on failed to update: Not sure if the program was hung up, I let it run for awhile and finally closed it with task manager. I then rebooted and ran the update and got the same failure as earlier. View attachment CBS.log Thanks
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 16, 2019 #36 How long did you wait?
P pestalent1 Contributor Joined Dec 20, 2018 Posts 42 Jan 17, 2019 #37 About 10-15 minutes. I just tried again, started at: This time "Farbar Recovery Scan Tool" did update. I stoped it at: Did update, same: Rebooted and ran update again: View attachment CBS.log View attachment Fixlog.txt Thanks
About 10-15 minutes. I just tried again, started at: This time "Farbar Recovery Scan Tool" did update. I stoped it at: Did update, same: Rebooted and ran update again: View attachment CBS.log View attachment Fixlog.txt Thanks
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 18, 2019 #38 It did update, but the fix didn't work: Please try the following file. Just the fix. Do not try updates. Attachments Fixlist.txt 943 bytes · Views: 1
It did update, but the fix didn't work: Please try the following file. Just the fix. Do not try updates.
P pestalent1 Contributor Joined Dec 20, 2018 Posts 42 Jan 18, 2019 #39 OK, I ran it and it said it was successful. I did not try windows update. View attachment Fixlog.txt Thanks
OK, I ran it and it said it was successful. I did not try windows update. View attachment Fixlog.txt Thanks
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 18, 2019 #40 Thank you! Now this fix: Attachments Fixlist.txt 1.4 KB · Views: 1