[DISCUSSION] Windows 10 1903/9 'FINAL' Build 18362/3.xxx (PC) [19H1/2 Release]

It wouldn't let me initially. It gave me the error that it couldn't write the reg key.
It's also possible that the downloaded windows cumulative update fixed it. I'm unsure.

 

Tried that one did nothing for me. Defender kept running

 

For what it's worth, Windows Defender Tamper Protection was disabled by default on my clean installation of Pro. So disabling Windows Defender with Winaero Tweaker was successful and quick as always.

Does anyone know why Tamper Protection seems to be enabled for some users and disabled for others? (clean install, in my case)

 

Sorry guys, but if I build a homemade iso where can I checks SHA or MD5 hashes to confirm the genuine homebrew?
my exemple: export 1 index from genuine consumer edition the new one iso isn't genuine.
am i wrong?

 

You need to login to view this posts content.

 

Some have nicer UIs though. I do agree that Defender, or Windows Security is good, been using it for a year maybe and the PC is clean. The firewall settings/rule creation though are atrocious compared to something like Kaspersky, to which i will return once Edge Chromium replaces old Edge (Kaspersky+Edge gives some sort of Event Viewer errors each boot, and Edge window crashes and recovers on each first start, quite annoying, even when Edge is not opened at all). There's also stuff like App control, which app is allowed to access what and so on, anti-banner that works on desktop apps, quite useful overall.

 

For me even during setup (specialize), it didn't accept the keys without stopping the service

Code:

net stop WinDefend /y || sc stop WinDefend
reg add "HKLM\SOFTWARE\Microsoft\Windows Defender\Features" /v TamperProtection /t REG_DWORD /d 0 /f
reg add "HKLM\SOFTWARE\Microsoft\Windows Defender\Spynet" /v SpyNetReporting /t REG_DWORD /d 0 /f
reg add "HKLM\SOFTWARE\Microsoft\Windows Defender\Spynet" /v SubmitSamplesConsent /t REG_DWORD /d 2 /f
reg add "HKLM\SOFTWARE\Microsoft\Windows Defender Security Center\Notifications" /v DisableEnhancedNotifications /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender" /v DisableAntiSpyware /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Features" /v TamperProtection /t REG_DWORD /d 0 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection" /v DisableRealtimeMonitoring /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection" /v DisableOnAccessProtection /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection" /v DisableScanOnRealtimeEnable /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\SmartScreen" /v ConfigureAppInstallControlEnabled /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\SmartScreen" /v ConfigureAppInstallControl /t REG_SZ /d Anywhere /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\UX Configuration" /v Notification_Suppress /t REG_DWORD /d 1 /f

 

I usually do these setting after apply (before first reboot), but I must admit I'm not sure if/ how this works with 18362.
I know JFX uses a similar method in WinNTSetup, I believe he added the TamperProtection setting in the latest WinNTSetup 3.9.4, but again I haven't tested this yet.

 

I have disabled Defender now with NTLite

 

UPDATE 4/26: We have released Build 18362.86 (KB4497093) for Windows Insiders who are currently on the Windows 10 May 2019 Update. This Cumulative Update includes the following fixes:

• This Cumulative Update includes the fix for Windows Insiders in the Fast ring who were unable to update to the latest 20H1 build from Build 18362.53.
• We have made general improvements for users in Japan or use the OS in Japanese including fixes for the Japanese IME and fixes for date and time issues.
• We fixed an issue where UWP VPN plugin apps might not be able to properly send packets through an established VPN tunnel on an IPv6 only network.
• We fixed the issue causing updating to Build 18362 to fail to install with an 0x80242016 error.

 

You need to login to view this posts content.

 

Perhaps I'm missing something but if you need to turn off/disable Defender why not just simply do it thru the setting provided in GP?

 

Not getting the new update through Windows Update...

 

Delete

 

My Windows 10.0.18362.53 > But I Do Not Have the Update 10.018362.86? I Already Click on Search, But it's Not

 

SHA or MD5 hashes are only useful for checking that you have downloaded / SVF-converted an ISO that is identical to the official source.

If you use other methods, e.g. UUP->ISO there will be differences, e.g. in timestamps, so the hash will be different