What do you guys do about updates on MS OS?

[BoxingChaos]

Is it me, or does the OS just begin to suck after updates? I am not just talking about one particular version, it seems like any time I begin doing updates on my pc, my computer just begins to act up. I sometimes just avoid them all together but that too comes at a price, feels like I damned if I do and damned if I don't.  The computer became very slow after updates too. So, how do you guys go about this? And please don't recommend another OS. 
Just got a lappy, and installed an older version of NOD32 smart security, did the lame windows updates and bam out went the firewall/s. I knew about this problem but was hoping I was special and it would not affect me  

[vissha]

Yes, I do accept MS and all its products are testing beta and our systems are testing lab rats - we are just a MiTM for their attacks.

 

Suggestion: U should try Askwoody.com Guides for Updates. It'll work perfect without any slow down. He'll always say the perfect time to update. Visit every day for keeping u updated on MS troubles.

Or best to move to Linux or Mac[Updated with latest firmware even if it is latest version OS]

[vissha]

5 minutes ago, 0bin said:

After every update I run this:

  Reveal hidden contents

rem USE AT OWN RISK AS IS WITHOUT WARRANTY OF ANY KIND !!!!!
 
rem Defrag HDD - Boot Windows USB - Repair - Troubleshoot - CMD - type/enter
rem c:
rem cd windows
rem cd system32
rem defrag c: /u
 
rem Decrypt and decompress system files
rem cipher /d /s:C:\
rem compact /CompactOs:never
 
fsutil usn deletejournal /d /n c:
chkdsk /scan
 
taskkill /im TiWorker.exe /f
net stop bits /y
net stop cryptSvc /y
net stop msiserver /y
net stop UsoSvc /y
net stop winmgmt /y
taskkill /im TiWorker.exe /f
net stop wuauserv /y
winmgmt /salvagerepository
 
del "C:\$Recycle.bin" /s /f /q
del "D:\$Recycle.bin" /s /f /q
del "E:\$Recycle.bin" /s /f /q
del "%LocalAppData%\Microsoft\Windows\INetCache" /s /f /q
del "%LocalAppData%\Microsoft\Windows\WebCache" /s /f /q
del "%temp%" /s /f /q
del "%WINDIR%\Logs" /s /f /q
del "%WINDIR%\Installer\$PatchCache$" /s /f /q
del "%WINDIR%\SoftwareDistribution" /s /f /q
del "%WINDIR%\System32\winevt\Logs" /s /f /q
del "%WINDIR%\Temp" /s /f /q
del "%WINDIR%\WinSxS\Backup" /s /f /q
 
vssadmin delete shadows /for=c: /all /quiet
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
cleanmgr /sageset:65535 & cleanmgr /sagerun:65535

 

It's good only when the update have 100% safe - no issues. Doing this will have more issues when the update is a botched and will lead to complicated issues when trying to uninstall/troubleshoot/trying workaround fixes.

 

2 minutes ago, 0bin said:

But sudo apt autoclean is good, not?

Yes, these cleaning post updates are good only in Linux since we have completely tested or stable updates which includes the issues after update and how to fix,... details when any update is released. However, In Windows, all cleaning of update logs and other traces/stuff related to the update has to be done only after few weeks or else at any certain point, we might be in hell with some hard botched update(s).

[virge]

I tend to find people who don't do updates tend to complain more when things don't work properly.

[dcs18]

Have got 2 identical rigs — one with Windows 8.1 and the other Windows 7. Then, the mirror image of the 8.1 is used to update hundreds of client machines.

 

Both are always kept updated to the very last Patch Tuesday (inclusive of OOB patches and HotFixes) and seem to be getting better with each update — especially the 8.1. Been receiving the exact same feedback from Customers about their own deployed systems which is an assortment of rigs, laptops, 2-in-1, etc., etc.

 

Guess it all boils down to the method employed to update one's system/s.