Phone Man

Build 17134.1 was released to the Preview Ring today. I updated my system and Memory Integrity option works the same. It is OFF and will wait on MB update. Jim

Just a heads up. MS released 1803 Build 17134 to fast ring today to fix problems with 17133. It will be tested in the Fast ring and move to Slow ring for more testing and then to Release Preview. Hopefully it will test OK and then released to the general public is the next few weeks. Hello Windows Insiders!Today, we are releasing Windows 10 Insider Preview Build 17134 (RS4) to Windows Insiders in the Fast ring. This build has no new features and includes the fixes from KB4100375 as well as some fixes for general reliability of the OS. As Build 17133 progressed through the rings, we discovered some reliability issues we wanted to fix. In certain cases, these reliability issues could have led to a higher percentage of (BSOD) on PCs for example. Instead of creating a Cumulative Update package to service these issues, we decided to create a new build with the fixes included. This just reinforces that Windows Insiders are critical to helping us find and fix issues before releasing feature updates to all our customers so thank you!No downtime for Hustle-As-A-Service,Dona <3

On my systems running Insider Build 17133.73 that option is OFF by default and that is why I did not have a problem. I turned it ON and after a restart MB Exploit Protect was OFF and would not turn on. I turned Memory Integrity OFF and after a restart MB is fine. I had to use the Reg file from the tutorial to turn it OFF. Jim

There are a few threads on here about that issue. MB is aware and working on fix. You can go back to 3.4.4 as it works fine. Jim

It is a know problem with Insider Build 17133. I recently installed W10 1803 Build 17133.1 from Slow ring and will stay on 3.4.4 until a fix is released. MB is working on the fix and should be ready very soon. I have a post over at Honorary Members on this problem. Jim

Looks like MS is still requiring the key. I have 2 systems that were not offered a cumulative update yesterday. KB4089848. Tried a bunch of times and no update. The key was missing and I added the key and then WU offered the update. Other people have seen the same thing. Both systems are running up to date Windows 10 1709 64it. One is running Windows Defender and the other Norton Security and both have MB Premium. I don't know what MS is doing but when I fail to get an update from WU my first move is to add the key. Confused but got it covered. Jim

On my systems I run Norton Security and MB Premium and MB is set to Never Register and all is fine. Last week while testing I removed NS on my laptop and that system is now running MS Windows Defender which is the default in Windows 10 and MB Premium. I set MB to Always Register and it shutdown WD and the Action Center showed that MB was handling Anti-Virus. So I now always have MB set to Never. Jim

After testing this, I found that it looks like MB will only set the key if it is registered with Window Action Center. I toggled that option between Always and Never and the key was set when it was registered and then deleted when it was not. I leave on Never as I use Norton Security and it also sets the key after some definition updates. On my Laptop I removed Norton and use Windows Defender and MB. WD also sets it after an update. The problem is with MB registered it disables WD. It must be a Windows 10 thing that removes the key after being shutdown for a while and is waiting for the installed AV product to update. The latest version of Norton has killed its Automatic Live Update function (Norton is trying to fix it) and I need to do a Manual Live Update to get it going. This key problem only showed up because Norton was not updating in a timely manner. Thanks for the information as I now know what triggers the setting of the key. Jim

Looks like the key is no longer needed with the latest Windows Cumulative Update and going forward. https://support.microsoft.com/en-us/help/4088776/windows-10-update-kb4088776 Jim

I agree, it is only used for MS to check before offering updates. That is how I found the problem. I was not offered the last Cumulative Update this past Tuesday as the key was missing. WU did offer some Office Product updates so they did not require the key. Just trying to understand the procedure that sets the key. It seams to depend on getting new virus updates but that does not always work. Jim

On my systems the key normally disappear over night with the systems off. And after boot in the morning the key is still missing. Running Norton update will restore the key if it updates some definition files but not always. On the other system with Windows Defender it also looses the key overnight and takes a definition update to restore and that does not always work. I do have a reg file I can use to manually set the key should I need it to run Windows Update but just trying to find what is going on. The big question is why are we loosing the key overnight. Jim

On my systems I have MB set to Never Register and am depending on Norton to handle the key. On my laptop I removed Norton and defaulted to Windows Defender and MBAM (not registered) and it also seems to loose the key overnight after a shutdown. Jim

Does it set it if it is not registered? And how is it set? The reason I ask is there seems to be a problem with this key being deleted when W10 is shutdown and sometimes it won't restore. Big discussion about it over at Norton Forums. I had a problem where WU KB4090913 would not show in WU and I found this key missing. https://community.norton.com/en/forums/windows-update-kb4090913-nsbu Just trying to understand what is happening. Jim

Is MB also required to set this key? Contact your antivirus manufacturer to verify that their software is compatible and that they have set the following REGKEY on the computer: Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD” Data="0x00000000”

On both my systems I had MB with Web Protection off. I got it to update to 1.0.3803. I then quit MB from the task bar and then checked Task Manager and after a few seconds the MB Service was gone. Restarted MB and all is back to normal. Jim