Dell System Detect errors...

:emotion-2:

I'd suggest uninstalling / reinstalling Dell System Detect. Type Settings onto [Cortana] search box, click Apps, select Apps & Feature, and then click Dell System Detect to uninstalled.  Please click on the link below to reinstall DST:

Dell System Detect | Dell US

1. Review the Terms and Conditions, check the box and click Continue.

2. Once the installer downloads, a notification window will appear asking if you want to install this application. Choose Install from this window.

3.Upon successful installation, a confirmation icon will appear in the Windows taskbar. Product detection will begin automatically.

Dell System Detect was uninstalled, then subsequently re-installed via your suggested link...

Initially all goes well but then it stalls with the error message ‘Running Dell System Detect.  Please wait while we detect your product.  This may take a few minutes.’   The progress bar is stuck halfway between 'Download & Install’ and 'Running Dell System Detect’.    However looking under Apps, Dell System Detect appears to have been installed.  Going to the DELL UK Support site and clicking Detect Product very quickly brings up my PC’s details.  So it would appear that the software, although appearing to stall has in fact installed.

If I now uninstall Dell System Detect and re-install it from:-

www.dell.com/.../scan

the software installs correctly...

So we’ll see what happens, as I seem to recollect doing this a few times before I’m not hopeful...

Thanks for your assistance.

Hopefully the problem is solved. Thanks for the update.

Sadly the problem is not solved...

Incidentally I did check for any required driver updates.  

All my drivers are current though there is a BIOS upgrade available.  I have BIOS version 1.3.5  dated 02/03/2017 installed whilst DELL recommends version 1.6.5 dated 03/10/2017.

Now I generally do not update BIOS files unless its absolutely necessary so I have not considered this.  This computer is only a few weeks old and I do not wish to have it bricked...

Thanks again for your help.

Event ID: 0 may be logged when you configure a Web Services Enhancements 3.0-based Web service to use a secure conversation: "An error occured processing an outgoing fault response"

You configure the application pool in Internet Information Services (IIS) to use a custom user account to run the Web service.

To work around this problem,  please use one of the following methods.

Method 1

Configure the application pool identity to run as a user account for which the user profile is already loaded. For example, configure the application pool identity to run as the Network Service account.

Method 2

Manually load the user profile of the application pool identity. To do this, use one of the following methods.

Method A

Follow these steps:

1. Use a user account to log on to the computer, and then do not change the user account.

2. Under this user account, create a Microsoft Windows service, or run a Windows service.

3. Configure the Windows service so that the user account can interact with the desktop.

Method B

To load the user profile, call the LoadUserProfile function.

Method 3

Disable the stateful SecurityContextToken object of the Web service by configuring the statefulSecurityContextToken element. For example, you can use the application configuration file that contains the following code to disable the stateful security tokens.

Method 4

To configure the Web service to use a secure conversation, use an X509 certificate, or use another security token type instead of using the default DPAPI implementation. To do this, configure the serviceToken element in the application configuration file of each Web server. For example, the following code configures the Web service to use an X509 certificate instead of using the default DPAPI implementation.

            " rel="nofollow noopener noreferrer">docs.oasis-open.org/.../oasis-200401-wss-wssecurity-secext-1.0.xsd">

              bBwPfItvKp3b6TNDq+14qs58VJQ= " rel="nofollow noopener noreferrer">docs.oasis-open.org/.../oasis-200401-wss-x509-token-profile-1.0

When you send a SOAP message, the stateful SecurityContextToken object is serialized together with an encrypted key that can be retrieved only by the Web service. On the contrary, the encrypted key of the stateless SecurityContextToken object is cached by the client and by the Web service. Therefore, a unique string that represents the cached SecurityContext security token must be sent in the SOAP message. When the caches are available, no problem occurs. If you use the stateless SecurityContextToken object and if the application domain that is hosting the Web service is reset, the caches are destroyed. Therefore, a SOAP error occurs.

Note Some virus scanners may cause the application domain to be reset. 

Steps to reproduce the problem

1. Open the WSE 3.0 Secure Conversation Quickstart sample. By default, this sample is in the following location:    drive:\Program Files\Microsoft WSE\v3.0\Samples\CS\QuickStart\Security\SecureConversation\Policy


2. Configure an application pool to use a custom user account to run the Web service in this sample. The user profile of the application pool identity is not loaded yet.

3. Run the WSE 3.0 Secure Conversation Quickstart sample.

harper_Alex - thanks for your reply.

I've read it a couple of times and I'll read it again but sadly I suspect it's all 'way' over my head.  I'm really appreciative for you taking the time to reply though.

Incidentally the complete error recorded is:-

  System.Xml.XmlException The '/' character, hexadecimal value 0x2F, cannot be included in a name. System.Xml at System.Xml.XmlDocument.CheckName(String name) at System.Xml.XmlElement..ctor(XmlName name, Boolean empty, XmlDocument doc) at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI) at System.Xml.XmlDocument.CreateElement(String name) at eSupport.Common.Client.Core.LastUpdatedHelper.SetLastUpdatedValue(String type, String value) UpdateLastUpdatedConfig 192.168.1.3

You'll obviously be aware of this already but for the information of anyone else reading this thread...

Thanks again for your input.

If Dell System Detect doesn't start then I suggest you click on the link below:

Dell System Detect could not be started in Windows 10 ...

LSUFAN51 - there is no problem with starting Dell System detect and it appears to run ok - the problem is that my Event Viewer reports  'Dell System Detect errors Event ID 0'  every single day - and always in pairs.