topic Re: 82.30 erasing the SetupConfig.ini contents in Endpoint

82.30 erasing the SetupConfig.ini contents

Andrew_Scott — Wed, 03 Jun 2020 00:05:18 GMT

Has anyone else seen this?

On several of our test systems, the SetupConfig.ini file is completely blank after upgrading to 82.30.0530.

The file has the correct FDE driver path in the ReflectDrivers section on systems that have not been upgraded yet.

Re: 82.30 erasing the SetupConfig.ini contents

PhoneBoy — Mon, 08 Jun 2020 03:20:47 GMT

How are you executing the upgrade?
Possibly relevant: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk120667

Re: 82.30 erasing the SetupConfig.ini contents

Andrew_Scott — Mon, 08 Jun 2020 15:36:37 GMT

I think you misread my issue.

The instructions state to use this command for UEFI systems in BCDBoot mode:

setup.exe /ConfigFile "%SystemDrive%\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini"

This is supposed to work because the file contains the the ReflectDrivers path that tells Windows how to handle encryption.

Here is the contents of SetupConfig.ini on a system running previous versions of Endpoint Security:

[SetupConfig]
ReflectDrivers="C:\Program Files (x86)\CheckPoint\Endpoint Security\Full Disk Encryption\Driver"
ResizeRecoveryPartition=Disable

DynamicUpdate=enable

After upgrading to 82.30.0530 though the SetupConfig.ini file is completely blank. This means that Windows no longer knows how to read the data on the FDE encrypted drive and fails the Feature Update.

There were versions about two years ago where the path was incorrectly entered with \\ in the path instead of \ which broke it too.

The file content just seems to be a consistent oversight in build QC.

Re: 82.30 erasing the SetupConfig.ini contents

PhoneBoy — Thu, 11 Jun 2020 02:24:54 GMT

I said "possibly" relevant because I wasn't quite understanding the implications of the issue. 🙂
In any case, I recommend a TAC case as this clearly shouldn't be happening.