Cumulative Update KB4512508 Windows 10 v1903 build 18362.295 - Aug. 13 Win Update

Well some of the methods I tried involved completely removing all Windows update components and replacing with donor components (from the laptop which was a known good subject), including removing the complete software distribution folder tree + Db's. That didn't work.
Each time I tried something I would run DISM and SFC with the relevant switches, and each time both would return no issues.
The desktop had accepted every single SSU, CU, Defender definition (even when MS changed to the new format) since I first clean installed 1903 the day it went on general release.
This was the first update to not be accepted, and as I said, looking through the Windows update logs it was quite clear why it was failing but how to fix it was another matter entirely. But whatever the reason for the glitch it is now purring along nicely, the repair install probably cleaned up some junk as well, so I'm ok with the result.

emailx45 said:

MSWindows 10 Pro 64bits Workstation build 1903...295 ok
CPU Intel i7 4770K, 8GB, nVidia GTX650 Ti Boost 2GB
Asus Saberttoth Z87 BIOS updated
Virtualization always was ON BIOS/Windows
I have Kaspersky KIS 2019, VirtualBox 6 and I can create VM by MSWindows too...

But I DONT HAVE "SANDBOX" in options from ADD FEATURES on MSWindows screen like yours.

any idea?

hug

Off the top of my head, Workstation isn't geared to playing around with, it's for, well, work. Bosses would raise an eyebrow if employees were play testing apps in the Sandbox. Of course this applies if you actually are in a work environment with Workstation Pro. If a home user (i.e. private) just running Workstation because you want to, and can, same restrictions anyway. Machine doesn't know where you are or why.

Ztruker said:

Just noticed since I installed the 295 update, when I use Alt+Esc to switch active windows, it's also including the windows that are minimized in the ones it switches to. This is new, never happened before and is very annoying.

This is not an insider build, can it still be reported through feedback?

Did some more testing and checking on other builds and it looks like this is the way it's supposed to work. I thought it only switched between open, active (non-minimized) windows. Oh well.

Look at Event Viewer, see if there is any clue in there what is causing the problem.
If you start it manually: net start apache, from a Elevated Command Prompt. does it give any error message or number?
What version of Apache?

Otherwise rollback to before KB4512508.

Edit: Also check the Apache error.log. Should be in the x:\Apachen.n\logs directory.

f14tomcat said:

Off the top of my head, Workstation isn't geared to playing around with, it's for, well, work. Bosses would raise an eyebrow if employees were play testing apps in the Sandbox. Of course this applies if you actually are in a work environment with Workstation Pro. If a home user (i.e. private) just running Workstation because you want to, and can, same restrictions anyway. Machine doesn't know where you are or why.

Kind of stupid in my opinion then.
Sandboxing at least the email client would be a great idea.
Remember when it comes to malware: You click it, you own it

emailx45 said:

MSWindows 10 Pro 64bits Workstation build 1903...295 ok
CPU Intel i7 4770K, 8GB, nVidia GTX650 Ti Boost 2GB
Asus Saberttoth Z87 BIOS updated
Virtualization always was ON BIOS/Windows
I have Kaspersky KIS 2019, VirtualBox 6 and I can create VM by MSWindows too...

But I DONT HAVE "SANDBOX" in options from ADD FEATURES on MSWindows screen like yours.

any idea?

hug

Like @f14tomcat said, it might not be included with the 10 Pro Workstation version
But!
If you feel like it, you can try this tutorial by @Brink : Enable Windows Sandbox Feature in Windows 10 Home Edition
That is for installing on the Win10 home version and see if it works for workstations too.
If it works, let brink know in the thread so he can add workstations to the tutorial also.