Windows 10: Tried to update to the April 2018 cumulative update and ended up having to completely reset...

I had an issue attempting this update around when it was first released. I turned off automatic updating then because my computer would only boot in safe mode and I had to reverse what happened with backup. I had trouble enabling windows updates again today but managed to allow a representative use remote access and fix the issues that I was having and to enable the updates again. I download and install the updates I missed since then, including the cumulative update. I prayed and hoped for the best that maybe Microsoft had fixed the errors that MULTIPLE people were having all over the internet with this particular update.


Nope.


I went to restart my computer after updating and my computer would not even boot in safe mode which was my safe guard against me having to reset it. I had no choice so I went ahead with resetting. Now it's just a pain downloading everything all over again and getting my computer back to the state that it was in before this disaster and I'm really not happy right now. I shouldn't have to fear that by trying to actually keep my computer safe from attacks and whatnot which is what many Windows updates are supposed to do that maybe someday I'm going to have to completely reinstall Windows. I would consider myself lucky that resetting worked and I didn't have to start totally fresh.


I wish Microsoft would look deep into these issues that Windows updates are causing because I know I'm not the only one! I've read forum after forum about this and I'm in disbelief. I feel sorry for those who can't even turn on their computers let alone be able to reset like I did. It's sad to see as I have always trusted Windows and rarely ever have issues. I feel like their ignoring the fact that their systems are failing because of their own work and they don't want to take fault for it.

:)

 

Windows 10 April 2018 Update(SCU) Partially Breaks MKV File Support?

I updated to main computer to the April 2018 Update, AKA Spring Creators Update, and it seems like they've taken a step backward with MKV file support. When I go into the properties of an MKV file on the Fall Creators Update, if I go to the details tab it gives me a bunch of detail about he media file, like resolution, framerate, audio information and bitrate. However, if I go into the same file's properties on the April 2018 Update, almost all of the information is blank, it only gives me a runtime and bitrate.

I really just want to confirm that this isn't just my computer and other's are experiencing the same thing.

FCU:




April 2018 Update:

 

2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892) - MS Surface 3

I have an MS Surface 3 (Not Pro) running Windows 10 Pro for Workstations, v1709 (Build 16299.15). When I search for updates, it wants to install 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892). It fails with Error
0x80070002.

I tried manually downloading the Delta and Cumulative updates and installing manually, but they fail stating it is not for my system.

How can I either:

• Get this update to install, or
• If it is not compatible, tell Update to not install it and ignore the update?

I have tried:

• Clearing the SoftwareDistribution folders and Catroot2 several times
• Running the Windows Update troubleshooter
• Every step in troubleshooting including try to run the Media Creation Tool
• Factory reset, including deleting all files and apps

After the Factory reset, updates applied but it again failed on 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892) with Error 0x80070002.

 

Microsoft Rolls Out Windows 10 April 2018 Update (build 1803)

This recent update is giving me anti-aliasing issues with my nVidia GT630M, when I use Flight Simulator X:SE. It was perfect before the update, which I received yesterday (April 30, 2018).

I tried everything but still get jagged edges around textures.

Am I the only one with this issue from the update?

Thanks,

Braden