Windows 10: Defender and 1803

It doesn't work for me either and I still find the old interface is better.

 

Having updated to 1803 from 1709 I now find when booting up defender takes a long time to complete.
When viewing the security centre blue dots are continually running on Virus threat protection and firewall and network. After about 1 minute the dots stop and the green tick appears. This is then followed by two Dcom errors in event viewer. So every time you boot you get these errors. Unfortunately APP ID and SID are unknown, yet it's telling you that this can be fixed with permission in Component Services.

This never happened in 1709. Both my machines suffer the same error. Not a big problem but, it's annoying to find this when the previous version on both machines was error free. Once again MS has taken one step forward and two steps backwards.*really

:)

 

How to get MRP on N edition of Windows 10?

Because its a Media related feature. The Media Feature Pack is not yet available for Windows 10 1803 which you running. Usually its not available until a week after launch and Windows 10 1803 is not expected to launch until April 10.

Why not install the non-N version of Windows 1803? Do you live in Europe why you are running Windows 10 1803?

 

loss of homegroup

Just connect directly through the Network showing in File Explorer on your computer running Windows10 version 1803. (Basically the same way you did before they created Homegroup.)

The problem is exacerbated by the computers not yet updated toversion 1803; they still want to use Homegroup and don't see the computers running version 1803 in Network,

 

This issue is caused by 2 registry entries that point to Defender features that are only available on Windows Enterprise (and maybe Windows for Workstations).

I think it is safe to delete these keys, BUT since I have not tested this, I don't recommend it. Maybe MS will issue a small patch for this in the near future.

 

Thanks for the reply, will wait to see if MS puts out a fix before I hack the registry.

 

@no1yak
Does the old UI works? C:\Program Files\Windows Defender\MSASCui.exe
Win+Run+MSASCui.exe

 

No it does not work!

 

As per slicendice statment - no.

 

Ok! The same effect is also true in 1709: MSASCuiL.exe does not open. We noticed that a few weeks ago on each upgrade attempt or even after a clean install(171xx.x). In the previous cycle, MSASCui.exe would take some 30 seconds to open, in this cycle they adopt a better strategy, it won't open.

Any changes in our favorite app get our immediate attention. 1803 will be 1803 when the normal condition will be restored.

<<For the better of final release, trying to kill data collection with a reg hack & al is an impossible mission with an Insider build. You should keep it the way it is, otherwise you'll get more problems.>>