Endpoint Protection

Hi all,

The Windows 10 Creators Update is expected to be released sometime in April 2017 unless MS hits a snag.   Any word if Ver 14 and Ver 12.1 will be ready for that update?  I am sure most of us will be delaying the update for a bit but I want to be proactive on this if possible.  I participate in the Insider program and am reading the current Build 15063 is expected to be the RTM Build.  Input from Symantec would be appreciated  

Thanks!

CQ

@Brian, are there still a lot of issues not resolved with MP1a.

Symantec will release the MP1a package on fileconnect confusingly leaving it named MP1 but the version number is different

Actually just downloaded MP1 says:

ProductName=Symantec Endpoint Protection
ProductVersion=14.0.2349.0100
 

Let's try it on C.U.

Update: non compatible 100%, error 1000 in mmc.exe and consent.exe on startup

Same as older version :(

Hi,

Can anyone tell me if 14.0.2349.0100 is, in fact, The MP1A release?  I have a case dealing with a high CPU usage which support has told me will be fixed by MP1A.  Still labeling it as MP1 certainly is confusing.

Thanks,

CQ

It's not listed so it just came out:

http://www.symantec.com/docs/TECH154475

Either support will need to confirm or a Symantec employee will need to update this thread.

Hi,

I received a clarification from my tech in support.  See the following answer about the 2349 release:

"This is an refreshed version of MP1 some promised fixes are not there in the 14.0 MP1 that is the reason this MP1 2349 version is released you cannot upgrade from 2332 to 2349 you have to uninstall and reinstall ,there is an other version is going to release by Symantec probably next month we still dont have ETA"

Sounds to me like the CPU fix I am looking for and possibly compatibility with the Creator's Update will be in the Symantec's April (maybe?) release. 

Thanks,

CQ

From my understanding this "hotfix" only solves an exception bug. Clients already on MP1 should fix them self using the new autopatch feature. Https://support.symantec.com/en_US/article.TECH239782.html

So do we have an ETA on when this will be resolved? We would like to begin testing the Creator's build in our environment but this is holding us back.

Would like to know this as well as the creators update is coming out on April 11th and the one test system we have running it now wont work with the latest 12.1 version. 

Greetings,

I wanted to jump in and help clarify things a bit for everyone.

1. 14 MP1 (14.0.2332.0100) and 14 MP1 Refresh (14.0.2349.0100)
   • This refresh was done specifically to address the issue outlined in: https://support.symantec.com/en_US/article.TECH239782.html. The build was refreshed to prevent anyone from running into this issue, going forward.
   • There is NO migration path from 14 MP1 (14.0.2332.0100) to 14 MP1 Refresh (14.0.2349.0100).
   • DO NOT attempt to migrate from 14 MP1 to 14 MP1 Refresh.
   • Both versions are considered current for all intents and purposes and the documentation will be updated to reflect this information shortly.
   • If you're already on 14 MP1 (14.0.2332.0100), make sure you've familiarized yourself with TECH239782 and have taken the necessary precautions to avoid the issue it describes. Your next upgrade opportunity will be the next Maintenance Patch or Release Update of Symantec Endpoint Protection.
2. Windows 10 Creators Update Support
   • We will update our documentation with our official support stance for the 12.1 and 14 product lines, shortly after Windows 10 Creators Update has been formally declared GA.
   • This is what we are planning to offer (subject to change):
     • 12.1 RU6 MP5 and above: Basic Support only (similar to what we did for Windows 10 Anniversary Update)
     • 14 MP1 and above: Full Support

None of this applies to pre-release/insider preview builds of Windows 10 Creators Update and we will not be offering any support for them.

Hope that helps!

Thanks!

Thank you David!

Currently 12.1 RU6 MP5 is blocked by windows creators update.  Is that going to change once MS goes final - or are we meant to override the app compatibility and install anyway?

Thanks

FYI today installed SEP 14.0.2332.0100 and Windows 10 Creators Update RTM installed without error.

So Creators Update is now releasee (at least for MSDN customers). So when can we expect a supported SEP version.

I just tried the official release of Windows 10 Creators Update (downloaded from MSDN), but it failed because it determined that SEP was not compatible (I am using SEP 12.1.6 MP7). Exactly the same happened last time Windows 10 was updated, so this is quite disappointing.

Symantec responded the other day with this:

https://www.symantec.com/connect/forums/windows-10-creators-update#comment-11796051

Creators update is available for more than just MSDN. You can get it using the Update Assistant so it is available to anyone. 

Symantec - Can you please confirm the comments above that 14.0.2332.0100 will not report compatibility issues. 

Yes, they replied that from MP5, basic support would be available, but it seems that is not true.

Hi David,

can you please eloaborate on couple of points below:

1. What exactly 'Basic Support' means? What features are missing/not available?

2. For those of us that are currently stuck on v12.1 (RU6 MP5 and above), will there be a release that fully supports the Creators Update?

Much appreicated.

Hi Mike,

That is correct. The compatibility assistant blocks by Microsoft are expected to be removed on or before April 11th.

Thanks!

Symantec - Can you also please confirm that 12.1 RU6 MP5 and above will not report compatibility issues on or before April 11th?

Hello Symantec,

Can we get a difinitive responce regarding the Windows 10 creators update (that launches tomorrow!!) and support for 12.1 RU6 MP5 .....

My earlier comments about Windows 10 Creators Update supportability still stand. Also, the blocks in place by Microsoft have now been removed for the aforementioned versions.

Thanks!

Looks like the removal of the compatibility block related to SEP 14 MP1 still isn't live. I'll provide another update once I get word that it has been removed.

Symantec Endpoint 12.1 RU6 MP7 is not working on Creators edition.

Symantec Endpoint 12.1 RU6 MP7 is now working on Windows 10 Creators edition (when running 12.1 RU6 MP7 and doing an in place upgrade to Windows 10 Creators edition.

I still can't get SEP 12.1 RU6 MP7 to install on Windows 10 Creators Update (Build 15063.138 to be exact). Continues to tell me that this version of Windows is not supported. Anyone else have luck yet?

It is working for me.

Hi All,

We're doing some last minute work with Microsoft on getting everything unblocked, so I wanted to add some clarifications and an update on where we're at with getting these final blocks removed.

Note 1 - The in-place upgrade block for 14 MP1 is targeted to be removed on 4/12/17. *During the upgrade process, Windows must be allowed to check for any important updates in order to remove the block.

Note 2 - The fresh install block is in the works to be removed as well. As soon as I have a firm ETA, I'll provide another update. In the interim, you can launch the install via the .MSI file instead of the Setup.exe in order to skip the compatibility check.

@David

Is it Symantec or Microsoft that is delaying the support?

It's all M$.

Bump (as Symantec haven't bothered to stick a subscribe button on ther forums website).

I just tried to update to Creators Update, but still the installer says that SEP is incompatible :( I am using SEP 12.1.6. MP7. I think this is due to the installers leaving behind stuff which Microsoft detects as old version...

As David suggested earlier... I installed via the MSI and it worked great! The only problem with that is you then have to do a Sylink drop afterwards, but it only takes a moment to do that!

What MSI are you talking about? An MSI installer for SEP or for Windows 10?

Same here. Upgrade with WSUS from 1611 to 1703 failed on SEP 12.1.6 MP5 German language

Same here. Upgrade with WSUS from 1611 to 1703 failed on SEP 12.1.6 MP5 German language

Same here. Upgrade with WSUS from 1611 to 1703 failed on SEP 12.1.6 MP5 German language

The MSI installer for the SEP client.

Just uninstalled Endpoint 12.1RU6MP5 (or similar version), upgraded to Creators Update 1703 using the Update Assistant, then installed Endpoint 14.0.0MP1.  Going fine

The solution with the MSI is probably when you either have a clean install or when you first uninstalled SEP before upgrading. I would like to upgrade my existing Windows 10 version without uninstalling SEP 12.1.6 MP7 first.

With new MP1 14.0.2349.0100 upgrade is successfull, with previuos MP1 version is a no deal...and symantec states there is "no difference", they say do not upgrade etc etc...I say upgrade and it work, and it's time for a real mp1a...

I upgraded to Version 1703 OS Build 15063.138

There were dozens of consent.exe errors in Reliabiliy History. 

A chat with Microsoft said do a complete refresh.

That would NOT run until I uninstalled SEP 14.0.0 MP1. 

But I had to restart after the uninstall and then before reinstalling Windows I turned on Windows Defender and checked. 

All the errors are gone!  Magic!

I had the same issue with a spare Insider Build machine and (not knowing the above) did a bare metal reinstall. No software added (including no SEP) but no errors.

So SEP V14.0.0 MP1 is NOT compliant with 1703 Build 15063.138

Windows Defender works fine, but hopefully a truly new version will come out SOON. All our clients use SEP.

I received an email from Symantec today, announcing EOL for 12.1x. I have already upgraded to 14, but I did have to install the MP1 refresh before I could upgrade to the Win 10 Creators version. I had to uninstall the desktop client, reboot, then push out the the new client package. Windows Defender is now showing up on the taskbar with an error about the firewall being disabled, but when you open it, it says the Symantec firewall is on.

Final Update:

*During the upgrade process, Windows must be allowed to check for any important updates in order to remove the block.

Note 1 - This final block is expected to be removed by Microsoft on May 9th, 2017. In the interim, you can launch the install via the .MSI file instead of the Setup.exe in order to skip the compatibility check.

Thank you for the reports in relation to the two silent mmc.exe and consent.exe errors observed in the event logs on system startup. We are investigating. The two errors do not impact functionality and appear to be cosmetic. Please feel free to open a case with Symantec Support for the latest updates on that issue. Refer the technician to TECH240364 if you proceed with that option. You can also subscribe to: https://support.symantec.com/en_US/article.TECH240364.html

Hope that helps!

Thank for investigating the reliablity errors. I hope you will be able to provide a new version to prevent this. 

Perhaps I am being picky, but I do not regard an overall Windows 10 reliablity of zero to be cosmetic. That is why I am hoping for a fix.Thank you .

It also appears that SEP 14 MP1 is causing Windows Malicious Sottware removal to stop working . I am seeing this on client and one of my own desktops running Windows 10 Pro 1607 OS Build 14393.1066 - one version behind my own laptop.

Again, thank you for your help here. 

May I ask which version of 14.0 MP1 is allowed now is it both 14.0.2332.0100 and 14.0.2349.0100

Hi Mike,

Both versions are allowed.

Thanks!

Hi,

I second Mike Tremmel's question about which MP1 will not be blocked.  In prior comments some are indicating that 14.0.2332.0100 is not compatible. Some clarification from Symantec would be appreciated.

Thanks,

CQ

I have tested upgrading windows 10 to windows 10 creators update with version 14.0.2332.0100 installed and it now does not ask to uninstall before upgrading. I used a USB stick created with the media creation tool and I also went to the microsoft media creation tool website and clicked upgrade now from there both options now work as long as you let setup check for updates first.

Thanks for the information Mike.  That is encouraging news.

It still doesn't work with SEP 12.1.6 RU6 MP6 Build 7061. I've tried the In-Place-Upgrade by executing Creators Update's Setup.exe from my Hard Disk. I enabled the Setup tool to search for updates but it still doesn't accept to upgrade Windows 10 Anniversary Update to Creators Update because of SEP.

@David-Z Please provide an ETA when this block will finally be removed. It still doesn't work as Symantec states.

Thank you.

On my Windows 10 Pro V1607 14393.1066 machine, I reinstalled SEP 14.0.0 MP1 Build 2349 (newest I can find) and that fixed error "Windows Malicous Software Removal stopped working" error. All is fine on this machine. 

However, Build 2349 sitll does not work correctly on Windows 10 V1703 15063.138. I am using Windows Defender on this machine until SEP catches up.

To obseve the trivially obvious:  Windows Defender works exceedingly well and is a definite and robust competitor to SEP. So if SEP does not catch up, it may fall by the wayside. 

Just tried installing SEP 12.1.7166.6700 on Windows 10 Build 15063 release as of yesterday, intall is blocked with compatibility assistant message "This app can't run on this PC" any proposed updates for fixes on the way.

HI, 

Is there any solutionon this, I just upgraded to Win10 update creator build 15063 yesterday and could not able to install SEP 12-1-6 MP6. 

Please your advice. It says, this SEP version does not work with this version of windows. It actaully really worked well with W10 build 14939.

Thanks

Rico 

HI all, 

I had earlier an hour ago posting that I could not able installing SEP 12-1-6 MP6 on Win10 update createor build 15036, I did the installation of SEP using 'setup.exe' found inside SEP12-1-6 MP6 directory and like I said, it did not work with error saying "this app does not work with this version of Windows".

But today I just managed to installe the SEP12-1-6 MO6, it accepted and now up running well. You know what I did? Instead click on 'setup.exe', I simply click on MSI file, yes 'Sep64.msi', it just worked for me, installed the SEP correctly and now my SEP is installed on Win10 Build 15063. 

FYI, I installed the W10 build 15036 from scracth, freash copy of windows after download the ISO when the Update Creater was announced. 

Thansk and hope it helps

Rico 

see my last post bro. 

Still no go for SEP 12.1.6 RU6 MP6 Build 7061 although the official Symantec page shows it as compatible for an upgrade to Windows 10 Creators Update. This is a pity and I expect some official word from Symantec on when this will work (at least an ETA).

It's not an option to uninstall/reinstall SEP.

Thanks and best regards,

Ronny

So the question is when? 

Symantec needs to make 2 versions of SEP.  One without Network Threat Protection and one with it. Win 10 has upgraded everytime with older (not the oldest) SEP clients that have the Network Threat Protection removed or never installed.

Hello,

I'm using the MSI file for the SEP  installation and it's work for me.

I hope this issue will be solved at the expected date (9th May 2017).

Thank you David-Z for the Compatibility information

Please explain "By using the MSI file"  I have lots of computer to reinstall Symantec on.

Hello Butch,

When you create a SEP package, you have an option to create an EXEC file. Remove this option, you will see all installation files, Use those files to install SEP on Windows 10 Creators,  execute the file  "Sep64.msi" to lunch the SEP installation.

Reporting back to also confirm that launching the .msi from the SEP client install folder is successful. Add a couple of observations. Since we use the Web based console at our enterprise, I export the SyLink for my organizational unit, then replace the default in the client install folder.

I have 3 machines:

1. WIndows 10 Pro Version 1607 Build 14393.1066 with SEP 14..0 MP1 Build 2349 - All works just fine and no reliability errors.

2. Windows 10 Pro Version 1703 Build 15063.138 using Windows Defender at this point.

3. Windows 10 Pro Version 1703 Build 16179 (Insider):

(a) With Windows Defender zero issues and zero reiliability errors.

(b) Add SEP 14.0 MP1 Build 2349 to this machine: Copious quantities of UI Consent Reliability Errors in Relaibility History.

No version of SEP exists that works properly and correctly with any 15,000 series or 16,000 series builds of Windows 10. 

This issue DOES need to be fixed by Symantec. It is easy prodcuce by taking a clean machine with no errors, installiing SEP and seeing the errors and then uninstalling SEP. I have done this with both 15,000 and 16,000 series machines. 

I hope we will see a new version soon.

Is there a solution yet to intalling v12 on a single client or PC? I dont think the MSI solution (for v14 only?) is applicable to installing on a single machine. In addtion is there an update on when MS will unblock the latest v12 on PC's with the windows 10 creators update installed?  Thanks!

Support for Windows 10 v1703 has been provided in PMImport v7.2.22 released on 4/25/17 per INFO4323. Schedule the Import Patch Data for Windows to download v7.2.22 and review the deployment process outlined on DOC9422.

Thanks to all of those who posted about using the MSI version of the installer. I created a new MSI package using release 12.1.6 MP7 (12.1.7166.6700) and it installed without any issues to Windows 10 v1703 build 15063.138. The same installer using the EXE still fails to run.

I second Richard's post above. Thanks

Support for Windows 10 v1703 has been provided in PMImport v7.2.22 ​

​​So far as I can see this is for the Managed Client and I have the Unmanaged Client. I do not have PMImport. 

I can install the client - it fails to work properly. Copious quantities of permission errors (UI Consent. exe). 

You really need a new version of SEP that just works correclty in Windows 10 Version 1703

What I am saying can be trivially observed on a Windows 10 1703 machine. Do a fresh install - zero reliability errors. Install SEP and copious quantiites of reliability errors.

I haven't found out how to subscribe to topics or it does not work, so posting a bump. Sorry :)

Another observation, we use SEP Manager 12.1.6 (12.1 RU6 MP7) build 7166 (12.1.7166.6700) web based console for package distribution. Observed on Win 10 1703 client running  12.1.7061.6600 SEP,when issuing upgrade from remote console it will not successfully install. The client confirms downloading and verifying the client, however it will not upgrade (ser attached).

Got any updates about the removal of the final block? It's May 9th and we still can't install SEP 12.1 RU6 MP5 on a fresh install of Win10 Creators Update via Setup.exe. Trying to figure out if it's our setup or if it just has not been removed yet.

The final fresh install block for SEP 12.1 RU6 MP5 and later was removed yesterday with Microsoft Update KB4016871.

Thanks!

Is there any update on a new version od SEP that will work in harmony with Windows 10 Version 1703 - that is without mountains of UI Consent.exe Errors in Reliability Monitor?  These errors are NOT cosmetic. 

We now have machines on deferred updates waiting for 1703 to install. We have to uninstall SEP before installing. 

I am concertned there is no update. If one has to repair V1703, Symantec Endppoint latest V14 versoin MUST be uninstalled before the repair will work. 

We need a version of SEP that works with Windows 10 V1703 or beyond. The current version does NOT work. Microsoft is relling out V1703 NOW. 

I have 14.0 MP2 running as of June 2. 

Some observations: 

A. For a domain connected, managed installation with Windows 10 V1703, SEP MP.0 MP1 2349 works without error. This was new last Thursday and I will check it again Monday. 

B. For any Windows 10 Veraion 1607 machine, SEP 14.0 MP1 and MP2 work just fine.

C: For Windows 10 Version 1703 and an UNMANAGED fresh installatoin of SEP 14.0 MP2, it still fails with Consent UI "stopped working" errors. 

So then apparantely the issue for versoin 1703 is an UNMANAGED installatoin from the folder SEPx64 from the Full Install downloaded file. 

(a) Is there a different way to install an Unmanaged client?  or a patch for the Unmanaged client?

(b) Can you fix the Unmanaged client?

Thank you., 

Sadly I was in error. Although the number of error occurences has decreased, they are still happening on a Managed Installation

The errors disappear entirely when I uninstall SEP and Windows 10 cannot be repaired unless SEP is uninstalled.

12.1.6 Ru6 MP6 gives error of Firewall not loaded, when is the the latest version of symantec available for deployment in corporate ?

@ John Hurst : I have tried installing without ABC component it installed fine​

​SEP 14.0 MP1 or MP2 both install fine on Windows 10 Pro 64-bit V1703 Creator Update.. But they do not work properly.

Managed SEP works tolerablly. A consent.exe permission error every other day or so

Unmanaged SEP is an entirely different issue. SEP (any version) does NOT work on V1703 Creator Update. Further, if you try a Windows 10 V1703 Repair Install, Windows will uninstall SEP. It DOES NOT WORK.

Symantec: This is trivail to test. Take a non-domain, Workgroup, Windows 10 Pro 64-bit V1703 machine and install SEP 14.0 MP Unmanaged from Setup in the SEP64 folder from the Full Install File available for download here. 

Restart the computer, open reliability history and look at the errors. 

Please: (a) fix your product, or (b) tell us you are not going to support Windows 10 in the future. 

Please answer.   Thank you.

I agree totally with John Hurst...  Symantec needs to fix these items...

I am waiting  for a fix to the item below.. Although microdoft  says that they are non-fatal errors my users (75 of them)  are locking for a few seconds

when in Outlook, excel  or even the webrowser...   Symantec said on july 13 they were working on this, today is july 25 and

no  update  nor any info update...   I am really  disappointed with Symantec  and their response to Windows 10 issues

Thnak you...

Environment

Just to add more to this subject

i  am running a Win 10 x64 enterprise (in domain)  Build 14393 with a SEP 12.1.6 MP6.

Even though i read on the comments that upgrading to creators update (1703) is feasible with version SEP 12.1.6 MP5+, for some reason i cannot upgrade windows.

I receive again the message that says that Symantec must be uninstalled before upgrading.

Can you please explain how can i fix this, assuming that uninstall is not an option currently? 

I have upgraded the server with SEP 12.1.6 MP8, but the exported client package cannot be used to install on client PCs, it damages Windows 10 build 1703 and I had to recover from the backup, or even worse than that I cannot repair Windows and need to make a clean installation.

May I know how to make all the clients PC protected with SEP on the latest Windows build?

I'm having issues installing too. I can't install SEP on a brand new Windows 10 build 1703 PC. I have tried MP6, MP7 and MP8. Up until now the MP7 installer used to work on Windows 10.

is any one from Symantec following up on this? Should be open a new thread? 

Have you fully uninstalled SEP and tried the upgrade again? Use cleanwipe if needed.