Bork Tuesday, Any Problems Yet?

Yes, but I can't even uninstall a update without it failing..

 

Installed all today's updates (IE Flash, Silverlight, Removal Tool and Cumulative update) on Win 10 Pro successfully and this time these updates are listed in the update history. Well done MS!

 

Yeah, that really didn't do anything. I ran SFC /SCANNOW and it found errors. But not sure how to read the cbs file.

 

Don't know as of yet. I installed WMSR Tool and all of MS Office updates. I'll wait on the other 10 updates until I find out what they are for. If for Win 10 I won't install

 

Same here, might even wait until SP1 comes out.

 

I haven't tried this but Brink is solid. For reading cbs after scannow, look at option 5 ---
http://www.tenforums.com/tutorials/2895-sfc-command-run-windows-10-a.html

 

http://www.sevenforums.com/windows-updates-activation/378265-patch-tuesday-august-2015-a.html

 

http://www.symantec.com/connect/blogs/microsoft-patch-tuesday-august-2015

 

Thanks for the helpful links, Dragon1952.

 

Could be due to this? http://www.infoworld.com/article/29...irms-patch-kb-3022345-breaks-sfc-scannow.html
I have this issue on my 8.1 machine; as far as I am aware MS have never fixed it ...
Edit: Also https://support.microsoft.com/en-us/kb/3022345?wa=wsignin1.0
http://www.bleepingcomputer.com/for...kb3022345-kb3068708-breaks-clean-sfc-scannow/

 

Windows Update Diagnostic Tool did not find anything, exploring other options (a screen window presented after telling it could not find anything) did trigger a repair in some sorts and Windows Pro did update, so tip of Ronjor did help

 

Thanks, I'll take a look at both.

 

Some MS patches are breaking SFC /scannow ...
Microsoft confirms patch KB 3022345 breaks SFC /scannow
I had to deal with it, and posted about it on this thread recently (July 23rd).
A fix is found here.
Don't know if this helps, but I hope so.

 

Thanks. I had to reinstall. Was that bad. I reinstalled W8, I might wait for a while before trying to upgrade again to 10.

 

After reading some of the links on the forum, I decided to download and install the remaining 10 updates for Windows 7. Computer is running fine and no nagware for Windows 10 so far, I'll keep my fingers crossed.

 

I see that KB2952664 has reintroduced itself to the list of available updates.
It's the update that nags users to upgrade to w10.
I hid the update previously, but like a waitress with a bad memory, it keeps coming back.

 

I am in the process of installing MS Updates on another (7x64) machine at this time. I'll report back.

Edit in: Since updating, I've been running that machine for about an hour and a half, and other than some initial sluggishness (I simply rebooted a 2nd time and it cleared up), all appears to be fine.

 

Updates now running with no troubles on two 7x64 machines.
I took them all with the exception of KB2952664, which I have hidden before but comes back each month I think.

 

The fix didn't work for me unfortunately (I think because the Windows version no. is different). Shows successful but sfc /scannow still shows the problem. Not sure whether to follow up with the author, or just leave it as MS says it isn't really a corruption - and supposedly will still provide a fix.

 

Microsoft Security Bulletins For August 2015

 

It's painful enough to go through this crap the first time, and it's no fun to comb through the ruins a second, third and fourth time.

Looking back, I see that I posted, "I have located a procedure for fixing the two corrupted files, and I am doing it now. First I uninstalled KB 3022345." Did you leave it on your machine or remove it?

In addition, I wrote, "I read that after renaming, one should be careful about running SFC again 'because SFC will attempt to replace the missing files and will demand CD/DVD insertion if it fails to find them'. Sounds like a reasonable warning to me. Rather than run the SFC again, I would be inclined to simply look for the file to see if a new one had been regenerated".

Very sorry to hear you have run into this issue as well. Good luck, paulderdash.