This was posted on the tenforums.com   Fixes/updates in the March 14 Win 10 update.
 
March 14, 2017—KB4013429 (OS Build 14393.953)

Improvements and fixes

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Addressed known issue called out in KB3213986. Users may experience delays while running 3D rendering apps with multiple monitors.
• Addressed issue in KB3213986 where the Cluster Service may not start automatically on the first reboot after applying the update.
• Addressed issue where the Active Directory Administrative Center (ADAC) crashes when attempting to modify any attribute of any user account in Active Directory.
• Addressed issue where the Japanese Input Method Editor is leaking graphics device interface resources, which causes windows to disappear or only partially render after typing approximately 100 sentences.
• Addressed an issue which improves the reliability of Enable-ClusterS2D PowerShell cmdlet.
• Addressed an issue where the Virtual Machine Management Service (Vmms.exe) may crash during a live migration of virtual machines.
• Improved the bandwidth of SSD/NVMe drives available to application workloads during S2D rebuild operations.
• Addressed issue where Work Folders clients get duplicate files (sync conflict files) when Work Folders is configured using Group Policy.
• Addressed an issue where Remote Desktop Servers crash with a Stop 0x27 in RxSelectAndSwitchPagingFileObject when RDP clients connect and utilize redirected drives, printers, or removable USB drives.
• Addressed issue where adjusting the Windows Server Update Services settings using the Group Policy feature causes downloads to fail.
• Addressed issue to hard code Microsoft's first-party provider registry key values.
• Addressed issue that causes the System Preparation (Sysprep) tool to fail.
• Addressed issue that causes Office 2016 profile corruption when used with User Experience Virtualization (UE-V) roaming.
• Addressed issue that causes the Local Security Authority Subsystem Service to become unresponsive after upgrading the OS.
• Addressed issue that causes the Local Security Authority Subsystem Service to fail when a SAP® application uses Transport Layer Security authentication.
• Addressed issue where sequencing large registries using the Application Virtualization 5.1 Sequencer results in missing registry keys in the final package.
• Addressed issue that fails to retain the sort order of names in a contact list after a device restarts when using the Japanese language.
• Addressed issue that causes transactions to fail because of a memory shortage.
• Addressed issue that allows files that are forbidden by the security zone setting to be opened in Internet Explorer.
• Addressed issue that causes Internet Explorer 11 to fail after installing KB3175443.
• Addressed issue that causes applications that use the VBScript engine to fail after applying KB3185319.
• Addressed issue that occurs in Internet Explorer when the CSS float style is set to "center" in a webpage.
• Addressed issue that occurs whenever the multipath IO attempts to log I/O statistics with no paths present.
• Addressed issue that causes a 32-bit static route added by a VPN solution to fail, which prevents users from establishing a connection through the VPN.
• Addressed issue that may decrease performance by up to 50% when Ethernet adapters that support receive side scaling (RSS) fail to re-enable RSS after a fault or system upgrade.
• Addressed issue to allow wildcards in the Allowed list field for the Point and Print Restrictions Group Policy.
• Addressed issue with multipath I/O failure that can lead to data corruption or application failures.
• Addressed issue that can lead to system failure when removing a multipath IO ID_ENTRY.
• Addressed issue that occurs when a Network Driver Interface Specification function NdisMFreeSharedMemory() is not called at the correct Interrupt Request Level.
• Addressed issue to utilize the proper service vault for Azure Backup integration.
• Addressed issue where SQL server takes 30 minutes to shut down on machines with a lot of RAM (>2TB).
• Addressed additional issues with updated time zone information, Internet Explorer, file server and clustering, wireless networking, Map apps, mobile upgrades for IoT, display rendering, USB 2.0 safe removal, multimedia, Direct3D, Microsoft Edge, enterprise security, Windows Server Update Services, storage networking, Remote Desktop, clustering, Windows Hyper-V, and Credential Guard.
• Security updates to Microsoft Edge, Internet Explorer, Microsoft Graphics Component, Internet Information Services, Windows SMB Server, Microsoft Windows PDF Library, Windows kernel-mode drivers, Microsoft Uniscribe, the Windows kernel, DirectShow, the Windows OS, and Windows Hyper-V.

Hopefully those are fixes instead of that other f word.

Long list ... none seems to relate to audio applications, though ...

Thanks for posting this Fireberd.

Thanks, but I think I'll follow my standard ops procedures by waiting a few weeks, then take a complete disk image backup, then update Windows and cross fingers

I updated my machines, went fine on 3, didn't work on the 4th (the only win10 home BTW). did a quick search and there are numerous pages out there alreday that it does not properly install, posting potential fixes ... but I didn't bother. let time and M$ solve it ...
 
the updated machines work as before BTW.

I think Microsoft Windows 10 updates are cowboy style! why you ask? Because the start icon F-ups and the message “Critical Error/Your Start Menu isn’t working. We’ll try to fix it the next time you sign in.” You may also see the error, “Critical Error/Start menu and Cortana aren’t working. We’ll try to fix it the next time you sign in.” The Microsoft Answers forum main thread for this problem is currently up to 73 pages, with 1,195 people chiming in that they’ve had the problem, too.
Short answer: Microsoft still hasn’t figured it out. Microsoft engineer Paul Sey says:
You may be able to temporarily resolve the issue by booting to Safe Mode, and then immediately booting back into normal mode. This workaround may resolve your problem for a while, however the error may return later.
Meanwhile you can't access your apps..One work around is to reinstall W10. It save your files but you got to reload your non-microsoft apps manually..are you kidding? Used to be with W7 you could fix your OS and save everything but not anymore.

What happens if you use:
 
"Windows Key + X" - shortcut for 'Run' where you could enter an application name for it to launch.
 
Or
 
"Windows Key + S" - shortcut for 'Search' where you could enter an application name and click on Apps, and then click on the application name from the search results.
 
Just trying to offer some alternatives - the Windows Start Menu is not currently failing on my system, so I don't know if whatever is broken for some folks would work.  Hope it helps, 
 
Bob Bone
 

I only have two PC's with Win 10, my desktop DAW PC with Win 10 Pro and a laptop with Win 10 Home.  Both work OK after the updates (and I've never had the problem hydemusic reports).  
 
I also have a dual boot on my DAW desktop system with the Win 10 Pro "Insider" beta version (currently up to build 15058).  I've never had that problem on that installation either.

Rob[atSound-Rehab]
Long list ... none seems to relate to audio applications, though ...

Could be (bold is mine)...there have been many reports of audio and video applications failing after Tuesday's update.

• Security updates to Microsoft Edge, Internet Explorer, Microsoft Graphics Component, Internet Information Services, Windows SMB Server, Microsoft Windows PDF Library, Windows kernel-mode drivers, Microsoft Uniscribe, the Windows kernel, DirectShow, the Windows OS, and Windows Hyper-V.