Driver error

And...  the issue continues.  re-enabled the scheduled task and still waiting for Dell to provide a fix.

Task scheduler works fine also for me, but definitively this seems something that Dell should be fix quickly.
My configuration Latitude 7300 with usb adapter Dell DA300.
Windows 10 Enterprise - Version: 20H2 - Build: 19042.572
The problem is not present if the DA300 is not connected.

I have been engaged with Dell support for several months now.

Not been entirely successful; I have sent logs and information, (including Windows event logs - which they didn't ask for but actually show the issue well), then Dell Support asks for same information and provides the same basic recommendations again. Seems to indicate that the history of the issue has been lost or they are just running through the basics without an skilled engineer looking at the basics of this.

So not hopeful; I think the issue is actually with Microsoft to resolve, but will keep pushing for a fix even if I end up swapping out the laptop (as the inbuilt microphone as also died)

Since I set (monitor off time) != (sleep time), I haven't seen the issue. Before they were both set to 5 min. Also no longer errors on the events log. No idea why this would make a difference, but from regular occurrence, I haven't hit the issue for 2 weeks.

Hi,
We have an update.
Our internal team have tested the LAT 7400 2in1 with the latest build 20H2 and the issue is not happening

Could you update the Windows to the latest build and try?

Also, can you check if under the power management tab from DM/HID (all of them), the option : ''allow this device to wake the computer'' is checked?

And the log you provided has only 4 events which's not sufficient for the investigation. 
Hence, please generate and send us the report with the same method 

Windows Deployment Logs
https://dell.to/3km74UT and install Microsoft UCS Log Tool from: https://dell.to/2IwDXBa External Link
2.Double click on the UCSLogTool link on the desktop.
https://dell.to/35lt2Df option 9 (General Windows log collection).
4.Type “no” for additional logs.
5.Type “n” for keeping temp files.
6.Capture the ZIP file the tool creates from the desktop (The file name reads similar to “v0.7.39.11_GeneralDataCollection_17134.rs4_release.180410-1804_201908191258.zip”) after the tool finished.

There are multiple threads on this, but other customers have already tested with 20H2 and issue is still occuring.

https://www.dell.com/community/XPS/Driver-error/m-p/7721925/highlight/true#M71924

I would have thought any test engineer would have tried to reproduce the issue (i.e. test on build 2004) then issue has been replicated, try and take steps to understand root cause and then test solutions such as upgrading OS.

Worth a try to upgrade though, so will give it a go, but I am pessimistic.  

All the HID devices in the DeviceManager which have a Power Management tab, have 'Allow the computer to turn off this device to save power' ticked, but the option to 'Allow this device to wake the computer' is disabled on all.  

I have provided full logs in the past, so not going to spend too much time capturing this again.

Hi,

I’d be glad to look into this for you right away. As our interaction would involve sharing sensitive information, I’d recommend that you private message us so that we can start working toward a resolution.

Just to confirm that I upgraded to 20H2 yesterday, and as expected, did not resolve the issue.

This morning the touchpad did not work after waking from sleep. Battery was nearly fully charged. MTCOnfig error in Event Log. Restarting PNPUTIL worked to fix it (which is a pain for me as I have to run the .bat file as admin to get this to work).  

Can confirm same behavior in device manager; the HID touchpad has no power management tab; but devices that do have the wake option disabled; like this example:

BTW; as another data point, this laptop has had the fix installed to allow kb/mouse on the thunderbolt docking station to wake the system.  It was the dell package, but that may be a reason why this issue is happening to some customers but has been harder to reproduce in the lab.

I will supply more Windows event logs to Dell support but had a production issue last night I am still working on so no time right now.

I would say that the issue is more of a problem when undocked. When docked I have external keyboard and mouse so don't even notice the touchpad going dead and when connected to power, the laptop sleeps less.

Typical failure happened today; closed laptop lid, went to customers site just down the road, opened laptop and touchpad was dead. Had to run my pnputil batch file with admin rights to quickly fix while the customer was waiting for me to connect to their BMS.

@ec-max - not sure that they have tried properly to reproduce in the lab. We had it working on Windows 10 Build 1909, then upgraded to Build 2004 and the touchpad stops working when it goes to sleep. They started with a laptop running 20H2 which is possibly different. 
I did wonder if it happens more often when running Linux VMs in the backup or RDP sessions, but not spent enough time to see if this is a factor. 

I checked that, and nope.. didn't happen 2 or 3 times.. but then failed again. 

cross-posting as this probably is the same for the XPS systems...  

https://www.dell.com/community/Latitude/Latitude-7400-Touchpad-erratic/m-p/7742025/highlight/true#M27829

Hi

on my Latitude 7300 I've just solved with this new driver

https://www.dell.com/support/home/de-de/drivers/DriversDetails?driverId=RDY6W 

NEW  Serial IO driver >>> Version 30.100.2020.7, A05 RELEASE  27TH- OCTOBER-2020

Unfortunatelly after deeper test I confirm that the issue is still present.
I reenable

pnputil /restart-device "HID\DELL08E0&Col02\5&1b86f367&0&0001"

Was already running this, and I got in to work this morning and Touchpad failed to wake up. 

Might be good to delete this post incase people find it and think it solves the problem.

My overall impression (which I posted to another thread on this, is that Dell have given up. There recommendation to me was to roll back to earlier versions of Windows.

I am intending to wipe the laptop and see if it can be swapped for something else as I have had enough. Just a minor annoyance but a regular one and with the microphone also dying on this laptop, I might as well invest the time and effort to clean out the laptop and set up another sooner rather than later.

This will no doubt cost Dell more than if they just had the right people look at the issue and get a fix put out. The work around came not from Dell, but from the community; and we don't have the tools and information that Dell have.