fearpoint
1803 screw up my system to where it wouldn't recognize my GPU or detect my gsync monitor.
 
Quickly reverted back which magically detects all my hardware and left Microsoft a message I hope somebody reads and then hangs their head in shame. I've never had problems with a windows update before let alone anything as absurd as what occurred after I installed that garbage.

My sound card was not recognizable and I uninstalled driver and couldn;t install new one before I boot system without sound card installed and remove all traces from PC and install again. I thought update from 1709 to 1803 will be finished on that.
Next morning, 12h later new huge Cumulative Update waited me, and my PC become not usable even during download that update after download finished. I restarted PC and couldn't boot him any more. 20h I didn't have PC, until I tried several options after 2-3 OS reinstall. Lucky for me mobo BIOS back SSD on fabric default for 3 seconds and I didn't had problem with that part. 
Now Cumulative Update shown on some pictures is hidden with tools and that's it.
 

 
Cumulative, and security updates were installed. Everything ok so far. It didn't even mess up my Creative sound settings this time. I'm surprised. It always messes it up. LOL.
 
 
EDIT: Two minor problems:
 
1) At Windows start. Sometimes the keyboard won't let me type my log on password into Windows.
 
2) Had a hard time correcting a misspelled word, because it wouldn't let me click on a certain letter inside a word. 
 
 
 

Iappera
I failed in the update last year.So I reject it,

I had a laptop that failed at an update a year ago but did the fall update just fine and has been getting them since.

So not only did that april update cause my hardware to not show up it also destroyed my geforce experience installation and I had to reinstall it after I reverted from that disaster windows update. 
Microsoft is now forcing that update even if users don't want it.
 
 

 
Windows just installed another Cumulative update. Will see how it goes.

If it's the one that ends in 403, that one has two issues -
https://support.microsoft...ws-10-update-kb4100403
 
1) May break multi-user mode in QuickBooks (workaround fix enclosed on KB page)
2) SMB1.0 (keep 2.0 and 3.0 enabled to prevent issues) (ditto)

NazcaC2
If it's the one that ends in 403, that one has two issues -
https://support.microsoft...ws-10-update-kb4100403
 
1) May break multi-user mode in QuickBooks (workaround fix enclosed on KB page)
2) SMB1.0 (keep 2.0 and 3.0 enabled to prevent issues) (ditto)

Good thing I don't have Quick Books.       =)

We have it at work but it was fine after that update (403), without having to manually install additional KB updates.

NazcaC2
We have it at work but it was fine after that update (403), without having to manually install additional KB updates.

Ah good.         

Windows 10 black screen problems fixed

June 2018 Patch Tuesday - released quality improvements and fixes for Windows 10 version 1803 or the Windows 10 April 2018 Update.
 
(excerpt)
 
The KB4284835 update moves Windows 10 version 1803 to OS Build 17134.112 and addresses an issue that caused systems to start up in a black screen: "This issue occurs because previous updates to the Spring Creators Update were incompatible with specific versions of PC tune-up utilities after installation."


This issue is separate to the black screen problems Avast users were struggling with last month after installing Windows 10 version 1803.


Among the other bug fixes, Microsoft has fixed an issue where firmware updates cause devices to go into BitLocker recovery mode when it's enabled, but Secure Boot is disabled or not present. This build now prevents firmware installation when a device is in this state.