FWIW, upgraded two computers to 1909 with Vegas 12 and no problems.

To point out how absurd this nonsense is, picture a carpenter who goes to work in the morning and discovers that, while he was sleeping, someone cut the handles off all his hammers.

Even someone who has fall back image(s) wastes time when she planned on doing something meaningful, like her cat video.

Here no problem with that update, immediatly followed by an update for the Intel driver of my laptop from signature

@Former user @j-v

It's apparently processor dependent. Perhaps it's being offered to some processors in error. I didn't go looking for it.

Details Here:

https://support.microsoft.com/en-us/help/4497165/kb4497165-intel-microcode-updates

As my PC's CPU is AMD I have no idea why this update is shown for me at all.

Scared and not updating for now. Thanks for the post.

Well, it gets curiouser and curiouser. I rendered a few of the same projects successfully after removing KB4497165. Then, I left the house for a couple of hours. On my return and restart, the render is failing again with KB4497165 nd without KB4497165.

I'll be restoring an earlier system image now.

same build   10.0.18363 like John, I9 9900k, no problems

I did all Windows Updates again. Reinstalled Vegas Pro 17-421 after uninstalling. I have had render failures and render successes. None have been obviously correlated to changes in the system. Image restore is on hold as I'd like to tinker with this a little longer.

I'm not certain that KB4497165 is the cause though the first change was coincident.

As my PC's CPU is AMD I have no idea why this update is shown for me at all.

Scared and not updating for now. Thanks for the post.

I don't believe you should ever manually update, but wait until it's forced upon you. Historically it's normally how the big upgrade disasters happen. You are a guinea pig if you choose to upgrade

@john_dennis Are you doing virtual machines with only 16 gb ram? Looks like you have it enabled in bios and have hyper-v extensions installed on the os.

@Howard-Vigorita

"Are you doing virtual machines..."

I'm not hosting virtual machines on this machine I do on other machines that I use. In fact, the machine was built by Dell and I've done little to change anything about it except to delete crap ware and replace the spinning disk with an SSD and an NVMe disk. I actually resisted buying a laptop when our last one failed since we have tablets etc. My wife bugged me until I finally bought it though she never uses it and we never go anywhere so the compromise of power for portability is moot for me.

I have used the machine for days on end sitting at the kitchen table when it's raining running video quality tests on that class of processor with QSV and Vegas 17-421. Aside from that, I've never done a video project with it and never had a failure. On the day of the failure, I started a project on another machine and rather than be anti-social, I decided that I would continue that project at the kitchen table.

It was at least two weeks since the machine had been powered up so I did a Windows Update to get it out of the way. I also ran the Dell Updater and dutifully accepted whatever that big corporation thought might be best for me, knowing that I could undo whatever came at me or re-image the machine.

My diagnosis after the post were so unrepeatable that I've stopped trying to debug what went wrong. Aside from running the household errands, I've:

• restored the factory image of the machine, applied all Windows Updates and saved the image.
• installed Windows 10 Professional from the latest ISO, applied all Windows Updates and saved the image.

I've not installed any editing software, but, as time permits, I will do so on each of these forks to try to determine what caused the failure if it returns. My preference is to use the fork without any help from Dell. I don't get any help from a Dell or anyone else with any of my other three machines and I seem to manage just fine.

My solution... I never update windows!

I think the delay is a good compromise. people who manual select Update are the first line of guinea pigs after the beta release, then when microsoft get enough positive signals they will auto update people with similar systems. these are the 2nd line of guinea pigs. So I put the 30day delay on patches, and 90day on feature updates. Gives Microsoft more time to roll back auto updates to problem system types when they detect bad signals.

Installed this update. All good for now.

I think the delay is a good compromise. people who manual select Update are the first line of guinea pigs after the beta release, then when microsoft get enough positive signals they will auto update people with similar systems. these are the 2nd line of guinea pigs. So I put the 30day delay on patches, and 90day on feature updates. Gives Microsoft more time to roll back auto updates to problem system types when they detect bad signals.

Microsoft has a new way of testing updates now. It's called the Windows Insider Program and you have to join to participate in which case you'll get every update as soon as it's released. Since that program started, updates have really slowed down and don't seem to get released at all until they make it into a cumulative update which appears to be coming out once a month now. Presumably the ones that are released earlier are deemed more critical in nature.

My practice is to update every time I go online to pull in Windows Defender Anti-Virus updates which are issued many times a day. I do block driver updates, however. Mostly due to compatibility issues with the newer Intel igpu drivers.