Main Forum > General Computer Support

Still not repaired the windows update error code 80245001

<< < (2/6) > >>

Boggin:
It seems strange that it is snagging sample pictures as I wouldn't have thought they would be related to WUs.

Have you tried opening a command prompt as an admin and running sfc /scannow to see what that reports ?

Edit

A couple of articles on MSDTC - but I'm not sure where you would find the MSDTC tab as described in the first article.

http://blogs.msdn.com/b/distributedservices/archive/2009/02/07/the-hidden-tool-msdtc-transaction-tracing.aspx

http://msdn.microsoft.com/en-gb/library/ms678917(v=vs.85).aspx

Sandro:
Same here. I just wonder if I need to reinstall all those samples to make it work or what? Wise Care 365 declared that it was safe to delte those samples before I did.

1. Have deleted the MSDTC log file and reinstalled the MSDTC.exe just as described here:

https://social.msdn.microsoft.com/Forums/en-US/a1643ee2-cbc2-40e4-a172-e342ab58c139/need-help-with-msdtc-errors?forum=windowstransactionsprogramming
http://thedbavault.blogspot.com/p/msdtc-uninstall-reinstall.html

Unfortunately, did not help to kill an error.

2. Got an idea that maybe the whole problem is involved somehow with .net frameworks. Have verified the frameworks and used the repair tool - everything seems to work just fine, but result regarding the windows update error is still negative. By the way, these tools you might use also for your Windows repair tool as those might help a lot of people. Check this out here:

http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx


This whole issue with windows update started after online upgrade from vista home premium 32 to 7 ultimate 32. I dont know maybe it is somehow connected with an error?!

Please check also a windows update error log along with other reports I received after processing the above-mentioned steps as attached in .cab file. Maybe you can trace a mistake out of it with your proffessional eye?

I shall try to get a fresh sfc report also ASAP.

Boggin:
It's Shane who has the professional eye and will leave those to him to peruse - I get lost off in those CBS logs as does the average user.  :smiley:

I'm always wary of Betas - how did you end up with .NET Framework 4.5.3 Beta installed.

I only have up to 4.5.1 but get WUs for up to 4.5.2

Aaron Stebner probably knows more about .NET Framework than MS does as it seems to have been a life-long work.

Shane doesn't have much faith in the .NET repair tool and just uninstalls/reinstalls them - but they have to be reinstalled in sequence.

Were you able to use the article for running MSDTC tracing ?

Shane:
This may seem odd, but I want you to try this.

OPen the windows disk cleaner, you might have to click the button to clean system files if this isnt in the list, but in the list you should see an option to cleanup windows updates.

MS put an update out a while back in Windows 7 where that option will cleanup and try to repair the winsxs folder and any old updates. Same thing as the dism in windows 8.

I have actually done this trick on a few systems and it worked. After you run it you will need to reboot and let it finish. Then we will try the windows updates again and if they still fail then we need to take a look at the cbs.log file to see if it can tell us why they failed. :wink:

Shane

Rick:

--- Quote from: Sandro on November 22, 2014, 11:44:01 pm ---Hi Boggin,

This information on readiness tool was helpful. I did not know those details before. Anyway, I have installed it again.... please check the log. It found a number of missing Windows media samples files - I let my Wise Care 365 deleted those some time ago as unneeded - and it found an error with MSDTC.log. I believe the real reason should be in MSDTC.log, right? I have tried to repair Msdtc with a hotfix I found on Microsoft website - did not work. I guess I will be re-installing Msdtc.exe now.

Unfortunately, your suggested command regsvr32 wups2.dll did not work either. Still showing me the same windows update error.

Any ideas?

Right Click on the CMD Command and open the CMD Command using the Administrator Account only, then try run again

Thanks!

--- End quote ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version