It's probably the coolest day of the future.

The group policy option to not reboot with logged on users has always worked for me with Pro edition. I imagine it would work for Home edition although you won't have the GP editor to set the registry values.

I believe Vivaldi is based on Chromium like Chrome is.

There's certainly an opening here. Chrome is too much of a memory hog and the latest firefox doesn't support as many extensions. If they can produce a non-memory hog version of chrome that supports all it's extensions that will make it a compelling alternative.

Not that I agree with it, but I believe MS is working on the assumption that they are the IT department for Windows 10 machines. Typically IT departments setup policies to force install updates to ensure the safety of their networks. MS is doing the same thing to prevent Win10 machines from being used as botnets. I think they got tired of being the punching bag on security and now they're enforcing updates. Sometimes you can't win.

You can off course still use group policy to get around the forced reboots. I'm not sure how well it will works for Home edition but it works perfectly for Professional edition. My Win10 machine has never force rebooted.

It's not worth it to allow the ads even if you like the content. What are you going to do when there's an exploit script in the ads that installs some ransomeware? It takes just one time and your system could be compromised.

http://dilbert.com/strip/1995-...

It takes courage to show a green line of death.

In the past that advice would have been good enough and you really didn't need AV. The issue is now even if you avoid running malicious software the bad guys can still take advantage of a bug in the OS or an application to get on to your system.

It's still true. Uninstall programs are still sloppy and Windows programmers still abuse the registry.

You understand why that was an issue under DOS? A .com file is interpreted as machine instructions directly and any process could execute a dangerous instruction. It hasn't been an issue since the WinNT days because of protected mode which limits the set of instructions that a user process can execute.

MS just wants users to be protected regardless of how it happens.

I agree it isn't ideal but most companies have these type of tests so you still have to be prepared. Usually they don't want a snap answer and want to see your thought process in solving the problem.

I agree with you but you have to understand the history. They get bashed for the poor security and tons of zombie Windows machines. Alot of that would be fixed by just installing the updates. As a result they go overboard in trying to make sure users install updates. Then they get bashed for that.