Upgrade to Windows 10 version 1903 may cause boot error on Windows 10 with ESET Endpoint Encryption

[TomasP 316]

We have identified a problem when upgrading a Windows 10 system with ESET Endpoint Encryption installed to the 1903 feature update. Installing the update can cause the system to crash (blue screen) when booting.

We are currently investigating the cause and recommend not upgrading an encrypted system to 1903 until further notice.

Systems that have been affected will need to be decrypted using our recovery tool (if full disk encryption was enabled) and then repaired using the Windows recovery console. See this knowledgebase article for more details: https://support.eset.com/kb7309/

[ThaDaVos 0]

Windows 10 1903 is starting to roll out - will upgrading be blocked if you have ESET Endpoint Encryption installed?
As far as I know this can be requested at Microsoft - don't know where though

[foneil 342]

10 hours ago, ThaDaVos said:

Windows 10 1903 is starting to roll out - will upgrading be blocked if you have ESET Endpoint Encryption installed?
As far as I know this can be requested at Microsoft - don't know where though

We do have this content available

"If you have not upgraded to Windows 1903 and you would like to prevent Windows from updating"

 https://support.eset.com/kb7309/#noupgradeyet 

[Jayce68 0]

Hi,
What's up ? Have you released a new version of ESET Deslock that is compatible with this update?
Been a long time without updating, especially at the security level ...

Thank you

[Daniel123 0]

On 13.06.2019 at 19:59, foneil said:

Mamy tę zawartość dostępną

„Jeśli nie dokonano aktualizacji do systemu Windows 1903 i chcesz uniemożliwić aktualizację systemu Windows”

 https://support.eset.com/kb7309/#noupgradeyet 

When will it be possible to safely install the 1903 update?

[Marcos 5,070]

Microsoft is going to block upgrade if ESET Endpoint Encryption is detected as a preventive measure until thet address an issue in the update caused by CleanMgr which accidentally deletes the FDE driver after upgrade but leaving it registered in the Upper Filter storage stack. The bug started to manifest in build 18343 and any newer builds are currently affected as well.

[Neil Marshall 0]

Is there any further updates on when this issue is going to be resolved, can we get a timeline?

[Marcos 5,070]

Please refer to https://support.eset.com/kb7309/

Cause

Due to changes Microsoft have made to Windows Feature update installations, upgrading machines to 1903 can cause systems to become unbootable. This is due to Windows 1903 performing a background clean-up task that removes the Full Disk Encryption (FDE) driver that ESET Endpoint Encryption (EEE) uses.

After working with Microsoft, they have now implemented a block to prevent the Windows 1903 update from installing on systems that are running an older version of EEE (pre v5.0.3). For more information regarding this block, please see the following article:

Windows Feature Update Fails to Install

[Neil Marshall 0]

Does this mean that the update works on version ESET Endpoint Encryption 5.0.1

 

[Marcos 5,070]

ESET Endpoint Encryption 5.0.3 is fully compatible with Windows 10 update 1903.

[Seth J 0]

FWIW - I still got a BSOD after upgrading to 5.0.3 before doing the windows 10 update.

Your repair .bat mostly worked - I didn't have a /dlpcore/upgrade/amd or /i386 folder, but the .sys was just in the 'upgrade' folder, so manually copying that to /system32/drivers/ fixed the problem.

Is this going to happen again with another update?  I'm looking at the machine now and confirmed it's ESET 5.0.3

[gotiengviet 0]

My winver 😊 It is still compatible well