Can't install Endpoint 10.6.1 on WIndows 10 -1903

[TomMorello]

Hello!
When will the full installer for Windows 10 1903 be available on the EPO console?

[smb24]

Based on the history of this product, I'm assuming never.

[spdif]

McAfee pulled the ENS July update because it was putting systems into a reboot loop.  Do not install the ENS July 2019 update.  https://kc.mcafee.com/corporate/index?page=content&id=SNS2062

When McAfee Agent tries to install ENS on Windows 1903 the ENS install script run by the agent reports the install was successful so the install script is defective.

I saw the EUA package creator was updated and (FINALLY!) allows slipstreaming updates into the installer.  I did this only to find that when the installer runs on the client it fails because...  its been an hour and I am still laughing...

Expected OS: <=10.0.17763

The OS version check has the wrong operator.  

Anyone tried creating a standalone package and deploying it with ePO?  That is my next step.

[spdif]

ENS Package Designer can't handle updates either.

[Former Member]

The Package Designer and the Package Creator and two different tools. The Designer is used to install the product with a set of predefined policies. The creator helps you package the installers and updates into one installer.

[Former Member]

The Update has not been pulled. It has been set to Release via Support only so that we can inform customers of the known issue prior to it being deployed. This is the KB you have referenced.
Also the McAfee Agent script merely shows the status of the script = if the script was run successfully then it'll show successful regardless of the actual status of the installation. Generally in the case of an installation failure, this is still part of the script and hence it shows as failed. In the reboot loop cases, the installation is successful.

I'm going to check the EUA package item you've just mentioned now.

[Sys_Admin]

Let's bring this up to date.

Had an email from the McAfee support desk yesterday.

'TENTATIVE' release date is now the END OF AUGUST!

Also according to the email ...

"Note: It is also not possible to provide the RTS of this patch as our engineers are in the process of re-building it."

Well done McAfee, when our renewal comes up early next year kiss goodbye to another long time customer.

[smb24]

Wow.  Unbelievable...

I'm curious if they truly understand the impact this has.  The people I've spoken with at support seem like they could truly not care less.  By the time (or IF) they release it again, 1909 will be on-deck for release.  

[TomMorello]

It is already dangerous that either update. The company incurs losses it is inadmissible! 

With such tendencies, my management is already thinking of switching to symantec.

[Former Member]

@Sys_Admin 

I can't believe it! End of August?????? Do they have any idea how many 1903 do we have in our networks? I have been defending this brand for years and now I can't even imagine explaining this situation to my colleagues!!!!!!!