Windows 10: Confusing Dell SupportAssist Test Results

Yeah, the only thing in the CBS.log is a known issue re: opencl.dll
It's a non-issue - so you have a clean bill of health as far as SFC is concerned.

 

So, my XPS 13 laptop passes the SFC, the F12 hardware diag., and all but the Extended testing offered by SupportAssist? Would you agree that basically there's evidently no real problem with this laptop? Apparently I'm experiencing issues with Dell's SupportAssist bloatware, not the laptop itself?

If so, then I see no reason to call Dell Support. I'll probably keep SupportAssist as a manual test for occasional non-Extended checkups - I've disabled its scheduled testing.

 

Everything in your first post indicates issues with the Dell tests: Failed to Start or Abnormal Exit.
You say your laptop seems to be running fine. Your SFC results indicate no issues with your OS. And yes, Classic Shell is a winner.
I wouldn't worry about anything; although, if no one calls Dell about problems with their Support software, how will they ever know to fix it? *Wink

 

That's true. Maybe I should call to let them know that their SupportAssist software is reporting Extended Test results that are misleading and therefore unhelpful. They might listen and make changes. Or not...

 

Up to you. If it were my software, I would want the feedback. *Wink

 

True. Consider it done, and thanks. *Smile

Any other comments about this thread before I close it as Solved?

Thanks to everyone for your invaluable assistance! *Biggrin

 

We'll be interested if a resolution is found while chatting with Dell, so don't forget us! *Wink

 

So, as promised, I called Dell Tech Support moments ago, and reported the same test findings to them that I've reported to you. They confirmed the same information you all have been offering: the F12 hardware test is the one they rely on, and the Extended portion of the SupportAssist test has been griped by many others for the same reasons I have complained about - random and spurious test failures from a working laptop. They said they were "working on it", and gave no update date. So, I asked them to add my name to the list of complainants, in case that would help spur an update to SupportAssist.

Are there any other issues I should confront regarding this adventure before I close this thread as Solved?

Thanks,

 

So, they are aware of the problem...okay. I'd get rid of it. You can always re-download it later, if you find Dell require it for something.

Well, you can keep an eye on your hard drive health with Crystal Disk Info. Other than that, I think you're good. Thanks for reporting back! *Smile

 

I think the confusing dell supportassist test results issue has been satisfactorily answered, both by Dell and TenForum Members.

I agree with simrick and take the sentiment even further - exorcise all of the Dell bloat from your machine. The software OEMs put on their machines offer little advantage over native Windows utilities.

There might be some 3rd party software packaged on the machine that you want to keep, but the Dell specific not so much *Wink

The choice is always yours on what to keep and what to uninstall - rule of thumb; if you don't use the software regularly or never use it ... get rid of it.

Yes, please mark your thread Solved.

Bill
.

 

Thanks for the update @Airpilot and for "taking one for the team".*Smile

As soon as I fire up my new Hell Dell Win10 box, I'll give the bloatware a whirl, solely for the purpose of adding my name to yours on the complainants list.

Cheers,

MM

 

FWIW, I downloaded and ran CrystalDiskInfo v.6.8.2, and, alas, it can't find my NVMe SSD on my Dell XPS 13 - "Disk Not Found". Their version notes state that they are aware of specific NVMe drives and have patched their s/w to report on some of them, but apparently the XPS 13 NVMe SSD isn't yet included. The s/w works fine on my two Win 7 GPT SSD drive PC's.

I sent them an email about this...

 

*Eek Oh the joys of being on the cutting bleeding-edge.

 

Thanks to all of you for your help. It's been a rush, and I'll continue to lurk when I can, in case I can help someone else. *Smile

 

Yeah I've seen that specific error. It has to be something internal with the programming. Guess they couldn't find the proper algebra geniuses like Apple has *Wink