we are having issues with detection logic on Windows 20H2, 1909 works fine. (as well as me posting on the free boards first) :P
Chrome and Webex giving errors of: Deployment type detection failed with error 0xc0000142
Performing detection of app deployment type Cisco Webex Productivity Tools 41.3.0.21(ScopeId_80429D8B-5171-4725-ABC3-DCC6EEED85CF/DeploymentType_26b7863f-31a9-492c-84b0-437455932a4a, revision 2) for user. AppDiscovery 3/2/2021 11:58:43 AM 15772 (0x3D9C)
Script Execution Returned :3221225794, Error Message: (null). [AppDT Id: ScopeId_80429D8B-5171-4725-ABC3-DCC6EEED85CF/DeploymentType_26b7863f-31a9-492c-84b0-437455932a4a, Revision: 2] AppDiscovery 3/2/2021 11:58:44 AM 15772 (0x3D9C)
CScriptHandler::DiscoverApp failed (0xc0000142). AppDiscovery 3/2/2021 11:58:44 AM 15772 (0x3D9C)
Deployment type detection failed with error 0xc0000142. AppDiscovery 3/2/2021 11:58:44 AM 15772 (0x3D9C)
Failed to perform detection of app deployment type Cisco Webex Productivity Tools 41.3.0.21(Cisco Webex Productivity Tools 41.3.0.21, revision 2) for user. Error 0xc0000142 AppDiscovery 3/2/2021 11:58:44 AM 15772 (0x3D9C)
Performing detection of app deployment type Google Chrome 88.0.4324.190 (x64)(ScopeId_80429D8B-5171-4725-ABC3-DCC6EEED85CF/DeploymentType_0b39cf71-2169-4f35-b852-fb6e5125b73d, revision 2) for user. AppDiscovery 3/2/2021 11:58:42 AM 15772 (0x3D9C)
Script Execution Returned :3221225794, Error Message: (null). [AppDT Id: ScopeId_80429D8B-5171-4725-ABC3-DCC6EEED85CF/DeploymentType_0b39cf71-2169-4f35-b852-fb6e5125b73d, Revision: 2] AppDiscovery 3/2/2021 11:58:43 AM 15772 (0x3D9C)
CScriptHandler::DiscoverApp failed (0xc0000142). AppDiscovery 3/2/2021 11:58:43 AM 15772 (0x3D9C)
Deployment type detection failed with error 0xc0000142. AppDiscovery 3/2/2021 11:58:43 AM 15772 (0x3D9C)
Failed to perform detection of app deployment type Google Chrome 88.0.4324.190 (x64)(Google Chrome 88.0.4324.190 (x64), revision 2) for user. Error 0xc0000142 AppDiscovery 3/2/2021 11:58:43 AM 15772 (0x3D9C)
Hello,
This is the first we are hearing of this issue. We have tested against 20H2 without issue.
It might be good to submit a ticket and provide the list of logs in the following link - https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#application-troubleshooting-client-logs
https://patchmypc.com/technical-support
UPDATE: We are only experiencing this on Dell Latitude 5520 models. Other models work ok. Thanks. No other action needed. Update: Cisco AMP bug in exploit protection for particular model..
We're having this same problem. What did you mean by "Cisco AMP bug in exploit protection for particular model..". We're running AMP and found that it is blocking conhost.exe, which is causing the problem. Did you find that this is a known issue?
For anyone else that stumbles across this, it's a known Cisco issue. Thanks to jspengler for sharing this:
[ExPrev] Issue with Tiger Lake Processors & Windows 10 20H2
CSCvx47570
Description
Symptom:
There is a compatibility issue between ExPrev and machines that have the latest Tiger Lake processors from Intel (released Sept 2020) and have Windows 10 20H2 installed.
The issue can cause 64 bit processes compiled with Microsoft's Control Flow Enforcement (CET) mechanism to crash.
Conditions:
AMP Windows Connector with ExPrev Enabled
Hardware: latest Tiger Lake processors from Intel (released Sept 2020)
Operation System: Windows 10 20H2
Workaround:
Disable ExPrev until 7.4.1 is released
Contact support to exclude the processes (applications) that have an incompatibility
Further Problem Description:
A fix for this issue will be made available in release 7.4.1 tentatively planned for late March 2021.
Details
Last Modified:
Mar 4,2021
Status:
Open
Severity:
3 Moderate
Product: (1)
Cisco AMP for Endpoints
Support Cases:
6
Thanks for providing an update!
We're having this same problem..
Cisco released 7.3.15.20174 with a fix. We've upgraded everything to that version and are now deploying 20H2 computers without a problem.
Quote from: Cody Mathis on March 02, 2021, 12:55:37 PM
Hello,
This is the first we are hearing of this issue. We have tested against 20H2 without issue.
It might be good to submit a ticket and provide the list of logs in the following link - https://patchmypc.com/collecting-log-files-for- (https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#application-troubleshooting-client-logs)employee monitoring (https://www.worktime.com/employee-monitoring)-patch-my-pc-support#application-troubleshooting-client-logs (https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#application-troubleshooting-client-logs)
https://patchmypc.com/technical-support
Hi!
Is everything okay now? I am experiencing the same issue on my Windows 20H2. Could you please give me some advice?
i also faced same issue on my dell laptop dickssportinggoods feedback (https://www.surveyzop.com/dickssportinggoods-feedback/) www.lowes.com survey (https://www.surveyzop.com/lowes-survey/)
Hi
If you are experiencing issues with detection on your clients, Please collect the relevant client side logs detailed in this article(https://patchmypc.com/collecting-log-files-for-patch-my-pc-support (https://patchmypc.com/collecting-log-files-for-patch-my-pc-support)) and send them to
[email protected]