Anyone noticed windows shuts down really fast with this update? With .125 it took like 20 seconds to turn off, now it barele takes 2 or 3 seconds.
Great, another CU that messes my system. This already happened with .98, which also shown a windows is updating % under the blue logo on install. After the update is installed (windows boots fine), and a Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase is done (or run windows update cleanup under disk cleanup), windows will throw a BSOD with inaccessible boot device after a restart. Only way to solve it is to run system restore and install via .msu, but the system restore wasn't even automatically created when installing .192.
Must be something local at your end, never have any problems on all systems i maintain or run myself.
This is only on one particular PC, and it happened with .98 and now with .192 since a fresh 1709 install when it came out. There's something to these two updates that when delivered via WU the install procedure is different. Only with those I get a % done text under the blue windows logo (then an auto reboot) after the first reboot (instead of only at log in), and it only turns problematic after a component cleanup, causing the BSOD. It could have to do with having an extra sata controller card, but windows startup repair can't fix it, so the only solution is a system restore. I'm now finishing a cleanup after installing the .192 update via .msu, as I had to to in past with .98. Hope to get it sorted. Edit:, it did. Again, the solution is to update via .msu, but I didn't expect this update to skip an auto restore point when installed via WU. Edit2: Tried another clean install with the .125 Dec iso only with ssd, and without any customization. WU installed the latest CU under the "normal" procedure after reboot, instead of the weird thing I was getting with % progression under blue logo, and no problems after a resetbase. I guess it was either a problem with the original 1709 iso installation that surfaces on that machine, or it's caused by some custom configuration such as enforcing the legacy boot (F8 text screen) that doesn't play well after a reset base on that particular PC because of an extra pci-e sata controller were the OS resides (hence the inaccessible boot device bsod).
I am currently on win 10 64 bit version 1709 build 16299.64 What should I do. So I download the manual update (offline) Is there a link please I am a newbie (noob) and thank you
I'm getting updates on WU today, today getting slow, seemingly to be stuck at installing 0%, 100%, now got it installed no performance decrease instead it made 3rd generation i5 faster. speaking of which Does patch also applies to 8-10 year old dual-core pentium CPU's which can run Windows 10 just fine? Or Intel too lazy to provide fix to decade old processor's?
MSRT going to be released on patch tuesday as usual?, though they always upload it on server way before like 2 weeks as seen from original timestamps
https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-254#post-1401419 Make sure the reg entry was set: https://forums.mydigitallife.net/th...9-64-16299-125-pc.75255/page-147#post-1401834
According to @Daz not many people run the specific jobs where the decrease in performance would be noticed, only on shared servers it will be really noticed but not on dedicated servers.