LandzDown Forum

Ok whoa horsey...so much good info for an aging man to take in..LOL

@ winchester...only one profile (me)
@Corrine thank you
@Pete I am sure that is it!!
@Dr. will do as Corrine advised

I n closing for now it definitely happens after any update from Micro
I still believe that it should be my/our/your option when updates are taken in

thank you G

all good now ad thank you ALL!!

Whew!  I'm glad that problem was solved.  As to installing the security updates, you've spent enough years on the forums to know what happens when people don't keep their device updated.  It is one thing to delay the version upgrade but when there are critical security updates, I personally don't choose to wait.

As to installing the security updates, you've spent enough years on the forums to know what happens when people don't keep their device updated.  It is one thing to delay the version upgrade but when there are critical security updates, I personally don't choose to wait.

I don't either. In fact, it is common for me on this, my primary computer, to check for and install any updates on Tuesdays, the day they traditionally are released.

I started doing this right away after migrating to Windows 10 primarily because I wanted to practice what I preached to my family and my clients. That is, "keep your operating systems current. That is a primary defense against the bad guys". I also wanted to install the updates first just in case there were problems - so I would be familiar with them (and how to fix them) should my clients call.

But as it was, problems didn't happen. Updates installed just fine. I didn't get any calls. Yes, over the years, there have been a couple (less than a handful) of hiccups. But worse case was fixed by a simple reboot.

Now I have encountered other computers that had problems after updates but what I discovered was those computers had many default settings that were changed by the user. They used 3rd party security programs, driver update utilities, and/or they dinked with virtual memory (page file) settings, and more. In many cases, those computers were older hardware - upgraded from W7. Hardware that often lacked solid W10 driver support from the HW maker.

Now I cannot and will not say those programs caused the problems, or that you will never have problems if you leave the defaults as Microsoft sets them. But it sure "seems", at least from here, that less problems occur if you just leave Windows alone. Contrary to what many want us to believe, the developers at Microsoft really are some pretty sharp people who know what they are doing. Not sure I can say that about the marketing folks, or some of the executive decisions made in Redmond, but the developers have done and are doing a good job.

[/Soap box]

a small update...found a little ditty that I am/have researched for a week
and works rather well at disabling windows 10 updates

what do you think?

StopWinUpdates
https://www.wilderssecurity.com/threads/stopwinupdates-disable-windows-10-updates.403499/

Quote

what do you think?

And for the record, I have never, not once, ever had Windows Update reboot my computer while I was using it without warning AND without providing me the opportunity to postpone the reboot.

Plus, Windows 10 has the option to set "Active Hours":

 --   Open Settings.
 --   Click on Update & Security.
 --   Click the Change active hours option.
 --   Specify the time range you're usually working on your device.
 --   Note: The maximum amount of time you can set is 18 hours ...
 --   Click the Save button.

My little 2 pense: I echo Corrine's & Bill's sentiments on Windows Updates, they should never be turned off or even delayed unless you are in an Enterprise situation and want to test the update before deploying to the main server.
This event also occurs on my WIndows 10 computers, especially the ones where I have the Insider Preview turned on. After an update, Edge opens up with a "Take a look at the new Edge" message and a short button click tour if you want. I just red x it and move on.