Windows Update (KB4497165) Caused Vegas 17-421 Render to Abend

john_dennis wrote on 5/21/2020, 2:27 PM

Dell Inspirion 5770

System Information report written at: 05/21/20 12:30:12
System Name: DELL-5770
[System Summary]

Item    Value    
OS Name    Microsoft Windows 10 Pro    
Version    10.0.18363 Build 18363    
Other OS Description     Not Available    
OS Manufacturer    Microsoft Corporation    
System Name    DELL-5770    
System Manufacturer    Dell Inc.    
System Model    Inspiron 5770    
System Type    x64-based PC    
System SKU    0811    
Processor    Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 1992 Mhz, 4 Core(s), 8 Logical Processor(s)    
BIOS Version/Date    Dell Inc. 1.2.5, 2/20/2020    
SMBIOS Version    3.0    
Embedded Controller Version    255.255    
BIOS Mode    UEFI    
BaseBoard Manufacturer    Dell Inc.    
BaseBoard Product    0XH3XD    
BaseBoard Version    A00    
Platform Role    Mobile    
Secure Boot State    On    
PCR7 Configuration    Elevation Required to View    
Windows Directory    C:\WINDOWS    
System Directory    C:\WINDOWS\system32    
Boot Device    \Device\HarddiskVolume1    
Locale    United States    
Hardware Abstraction Layer    Version = "10.0.18362.752"    
User Name    DELL-5770\John    
Time Zone    Pacific Daylight Time    
Installed Physical Memory (RAM)    16.0 GB    
Total Physical Memory    15.9 GB    
Available Physical Memory    7.74 GB    
Total Virtual Memory    18.3 GB    
Available Virtual Memory    8.45 GB    
Page File Space    2.38 GB    
Page File    C:\pagefile.sys    
Kernel DMA Protection    Off    
Virtualization-based security    Not enabled    
Device Encryption Support    Elevation Required to View    
Hyper-V - VM Monitor Mode Extensions    Yes    
Hyper-V - Second Level Address Translation Extensions    Yes    
Hyper-V - Virtualization Enabled in Firmware    Yes    
Hyper-V - Data Execution Protection    Yes

Comments

Musicvid wrote on 5/21/2020, 2:34 PM

Happened to me with update to 1909. Had to build from recovery because the update was corrupt and wouldn't uninstall.

Former user wrote on 5/21/2020, 2:37 PM

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

john_dennis wrote on 5/21/2020, 2:41 PM

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.

j-v wrote on 5/21/2020, 2:51 PM

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

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 451.48 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

john_dennis wrote on 5/21/2020, 2:58 PM

@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

fifonik wrote on 5/21/2020, 4:34 PM

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.

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X (not OC), RAM: G'Skill 16 GB DDR4@3200 (not OC), Graphics card: MSI RX580 8GB (factory OC), SSD: Samsung 970 Evo+ NVMe 500MB (OS), HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

john_dennis wrote on 5/21/2020, 5:31 PM

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.

frmax wrote on 5/21/2020, 5:32 PM

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

john_dennis wrote on 5/21/2020, 6:36 PM

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.

lenard-p wrote on 5/22/2020, 10:37 PM

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

Howard-Vigorita wrote on 5/22/2020, 11:46 PM

@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.

Cameras: Canon XF305, JVC GV-LS2, Canon 6D w/L-glass line. (Mar 2020: testing Zcam E2)
Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX5700xt Navi 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire Nitro+ Vega64 8gb graphics)
currently Vegas 17.452

john_dennis wrote on 5/23/2020, 1:05 AM

@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.

Steve_Rhoden wrote on 5/23/2020, 2:57 AM

My solution... I never update windows!

lenard-p wrote on 5/23/2020, 3:37 AM

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.

fifonik wrote on 5/23/2020, 4:54 AM

Installed this update. All good for now.

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X (not OC), RAM: G'Skill 16 GB DDR4@3200 (not OC), Graphics card: MSI RX580 8GB (factory OC), SSD: Samsung 970 Evo+ NVMe 500MB (OS), HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

Howard-Vigorita wrote on 5/25/2020, 12:26 PM

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.

Cameras: Canon XF305, JVC GV-LS2, Canon 6D w/L-glass line. (Mar 2020: testing Zcam E2)
Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX5700xt Navi 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire Nitro+ Vega64 8gb graphics)
currently Vegas 17.452

lenard-p wrote on 5/25/2020, 6:06 PM

Windows 10 KB4549951 update got me and many others. For me it did not ruin my system it just constantly blue screen of death'd when trying to restart after update, but was able to roll back. For others it did all sorts of damage and many had to factory restore. You can get the updates faster if you manually click on update but uncertain if I did that . It's manual updaters that are more likely to get their windows damaged. For the april update there were numerous people in the insider program that said they did report the faults before release but it was released anyway