Endpoint Protection

 View Only

  • 1.  Windows 10 boot problem

    Posted Feb 08, 2017 11:21 AM

    I want to install a client on a windows 10 pc.

    After the installation of the client Windows boot process shows "Preparing Automatic Repair", then "Diagnosing your PC", and then shows an Automatic Repair window that shows "Your PC did not start correctly..."

    If I go to "Startup Settings" in the windows recovery console and choose "Disable early launch anti-malware protection" I get the same result. If I choose "Disable driver signature enforcement" windows can boot.

    I read this page:

    http://www.symantec.com/connect/ideas/early-launch-anti-malware-issue-secure-boot-enabled

    I tried to solve the problem by creating an install package with a policy that has "eary-launch-anti-malware" disabled. But this did not help.

    Any idea how to solve this problem without disabling driver signature enforcement?

    Thanks a lot for your help

     



  • 2.  RE: Windows 10 boot problem

    Posted Feb 08, 2017 11:46 AM

    What is the exact version of SEP you're trying to install?



  • 3.  RE: Windows 10 boot problem

    Posted Feb 08, 2017 12:11 PM

    Problem is with driver and its signining, does it work if you uninstall SEP completely and reboot?

    Do you have Network threat protection  component installed ? Can you check in Device management if any drivers are showing up an Exlamation sign...



  • 4.  RE: Windows 10 boot problem

    Posted Feb 08, 2017 03:27 PM

    What version of SEP are you installing?



  • 5.  RE: Windows 10 boot problem

    Posted Feb 09, 2017 07:24 AM

    Thanks a lot for your fast anwsers. That is really amazing.

    > What version of SEP are you installing?

    Client and Server: 14.0.1904

    >Problem is with driver and its signining, does it work if you uninstall SEP completely and reboot?

    Yes after an uninstall all is working fine.

    > Can you check in Device management if any drivers are showing up an Exlamation sign...

    I checked all visible and hidden device. Only the PS/2 keyboard and PS2 mouse show exlamation signs because there are no devices connected. But this is notice is correct. The computer use an usb mouse and keyboard. But just to be sure I disabled the PS/2 deviced, but this did not change the boot behaviour.



  • 6.  RE: Windows 10 boot problem

    Posted Feb 09, 2017 08:43 AM

    What do you get when you install the unmanaged client?

    Same problem?



  • 7.  RE: Windows 10 boot problem

    Posted Feb 13, 2017 10:39 AM

    > What do you get when you install the unmanaged client? Same problem?

    yes, same problem.

    If I turn off Secure boot in the bios the problem does not appear anymore

    Here some information about the client:

    It is a HP ProOne 600 G1 computer with Windows 10. It is freshly installed. No additional software or drivers are installed.



  • 8.  RE: Windows 10 boot problem

    Posted Feb 13, 2017 10:46 AM

    I don't see anything in the notes in regards to an incompatibility with Secure Boot and Symantec has stated that 14 is fully supported on Windows 10. You may need to open a support case to have them look at it.



  • 9.  RE: Windows 10 boot problem

    Posted Feb 14, 2017 09:58 AM
      |   view attached

    The certification of the package installer is expired. Is that related with the problem? How can I renew the certificate?

     

     



  • 10.  RE: Windows 10 boot problem
    Best Answer

    Posted Feb 20, 2017 09:52 AM

    I solved it: The problem was the expired symantec certificat of the 14.0.1904 version (see above).

    I could solve it by installing the new version 14.0.2332 which has certificate that is valid until the end of 2017.