Breakdown....


Bulletin 1 Critical
Remote Code Execution
May require restart
Microsoft Office

Bulletin 2 Critical
Remote Code Execution
May require restart
Microsoft Windows, Microsoft .NET Framework, Microsoft Silverlight,
Microsoft Office

Bulletin 3 Critical
Remote Code Execution
May require restart
Microsoft Windows, Microsoft .NET Framework

Bulletin 4 Important
Remote Code Execution
May require restart
Microsoft Office

Bulletin 5 Important
Remote Code Execution
May require restart
Microsoft Office

Bulletin 6 Important
Elevation of Privilege
Requires restart
Microsoft Windows

Bulletin 7 Important
Elevation of Privilege
Requires restart
Microsoft Windows

I can't help but wonder, when the day will come, when patches overwhelm, pc resources..
I mean gigabytes of patches and programs running, adds up on any system. I wonder how much better, a pc would run, with none of that stuff on it.
I'd think it would be, significantly better.

Generally patches change or replace something, they don't run on top of what they patched. So probably about the same. That's why a "fully patched" Windows XP SP3 still fits on a CD :)

D007I can't help but wonder, when the day will come, when patches overwhelm, pc resources..
I mean gigabytes of patches and programs running, adds up on any system. I wonder how much better, a pc would run, with none of that stuff on it.
I'd think it would be, significantly better.

not if the patch is to fix an issue whereby your pc hangs or slows down while running something, patches are a neccessary evil due to the variety and amount of People involved in the tech industry and beyond and a patch is applied, it doesnt often run more then the once on install

As always 99% patches to prevent remote code execution. Bug fixing, performance and stability improving are more needed.

Windows 7 should be due for Service Pack 2 soon...

RophGenerally patches change or replace something, they don't run on top of what they patched. So probably about the same. That's why a "fully patched" Windows XP SP3 still fits on a CD :)

Not true for Vista and 7 unfortunately. The patches move the replaced files into some obscure folder on Windows System where it keep growing and growing ...And yes, you CANNOT delete those old files, even if nobody will EVER use those again...

Prima.Verayou CANNOT delete those old files, even if nobody will EVER use those again...

You can. Winsxs (vista, 2008, win7, win8) folder can be cleaned via dism

everythingsysadmin.wordpress.com/2011/03/16/cleanup-winsxs-after-windows-7-sp1-install/

There is a folder in Windows 7 where all the patches from Windows Update goes. You can delete these to save space.
In fact, there are instructions regarding how to do exactly that in some of the better Windows 7 SSD optimization guides.

Windows Update download cache : C:\Windows\SoftwareDistribution\Download
Delete that to free up space.

Hope I will get those updates for my Server 2008 R2 too.

DroneAs always 99% patches to prevent remote code execution. Bug fixing, performance and stability improving are more needed.

I agree ,BUT (yes a big BUTT)we will never have the other 2 if we can not stop most of the haxers out there that use remote code for there gain...just a butt....to think about.