Spam by adding random parts of sentences in it.
@bondsbw: No. It's just "an ordinary Office update crashed Outlook, on Win7 I can uninstall and hide the update, but what if I'm on Win10 where there will no longer be UI to allow me doing it" type of question.
And regarding whether "the update policy for Windows 10 also applies to non-Windows applications like Office", the policy is not but the UI is.
@magicalclick: It's not the first time when Office having security related updates, it'll crash certain Add-ins.
Afterall, there are so many Add-ins on the market... Antivirus, Translators, CRM/ERP, Workflow (Those which drain approve/reject response to system through VBA forms), Social Apps, or even in-house SI components. There's no possibility Microsoft can test every single one of them.
It's one thing having fast/slow lane cannot help to solve.
@BitFlipper: I didn't tried it myself, but seems someone figured out how to handle the 32/64-bit P/Invoke difference.
@kettch: I know. Had I read it I should have run "shutdown -a" myself. But for ordinary user they don't know about it. There have to be some kind of option to allow them to abort the reboot.
@Sven Groot: : That's good. Now if there is a button on the "you machine is about to reboot in..." prompt to link you there...
@GreyLensman: My thought is the opposite. Since many people still running 32-bit version of Windows (*cough* WinXP *cough*), changing the target platform to x64 is going to upset lots of people.
Instead, I try to make sure all assemblies inside my project are MSIL one. If you need to use Crystal Report it's okay. We ship with both 32-bit and 64-bit version of runtime so it'll bind correct on any of the systems.
IMO the only reason of having problem with "Any CPU" is because the project mangement (be it PM or team lead) is not properly managing the project.
@Sven Groot: No. I use manual update option, and see the message that it'll reboot after 4-minutes-something some time after I installed the updates. The two options I can select are "Reboot now" and "Close". The machine rebooted automatically several minutes after I selected the "Close" option and the work that I have on hand is lost because at that time I just thought it's the usual "postpone" button you get in Win7 and didn't read carefully. The several days argument is not reality.
My machine is Surface Pro 3, and I usually install update roughly one hour before I go to bed, if it need to reboot, I have no problem to let it reboot. (Afterall, I manually started the update)
I don't have spare machine to install Win10 so never tried that, but from the screen caps I see on the web, I can't find such option to specify when to reboot. If you can confirm that such option exist on non-business line of Win10, that's good.
On Win8 update, it'll force you to reboot when update is completed, without any UI option to suspend/delay the reboot. And even when they do this, it tell you that "you can keep doing your work while updating", while we know it's best for you to just stop doing your work if the work is a time consuming one that'll take a long time to save. And there's no warning anywhere on Windows Update UI that tell you about it.
For Win10, there is more concern when Microsoft decided they should take away more choice from users... The paragraph you quote is one, but there are others too.
So back to the basic, why do Microsoft think it's good to take away choice from users in the beginning? IMO setting sensible default is good enough. And I don't mind if the machine has joined domain and under control of WSUS/MOM so you WindowsUpdate disable parts of UI because the setting is under control of others.
When you are the sole owner of system, you should be able to tell it when it can stop it's work. If you cannot, by defination the system is broken and you had better fix it. Even if it means you have to fallback to an old system that actually works, or God forbids... install a modified system that disabled all these nonsense.
Since people more or less will be forced away from choice one with number of supported hardware, now you're left with choice two - disable Windows Update, and Microsoft comes back to step one where people just disable Windows Update or never choose to install update. What good does the decision gives?
The force reboot part sounds particularly lame to me.
For server SKUs, each process has right to delay shutdown for 5 minute, they may get away from it with clean shutdown. Since Vista each process on Consumer SKUs has only 2 seconds to do cleanup. That means applications with lots to write when quit will do incomplete write on shutdown, and with transactionaly write on NTFS, it means your previous work is gone.
Don't think it's acceptable behaviour because there aren't much such application. For system as popular as Windows, one in a million is next Tuesday.
1) No. I'm just requesting "user can have choice on whether reboot after update". The current UI have no way for you to stop reboot after the update. If you're in the middle of something and don't know how to use command line to stop the reboot, you'll be screwed.
2) Again, no. I'm just asking for ways to stop the update when there is *known* problem with current set of updates.
Q: If you know installing something will break your computer, what should you do?
A: Don't install it.
3) See (1).
4) If it cannot, just don't and provide option to manually control when to update instead.
Btw, on WinXP this question has an answer:
6) Not true. But currently (actually every version of Windows Update from Win98 to Win8.X) has it.
I can't see how it cannot be done. All we want is status quo we see on WinXP/Win7.