Dear Ten,
Forgive me if this is answered elsewhere...

Where to begin? Two Query's Mouse and setup log errors. TIA

This computer was built on 4-12-2021 , I've had nothing but problems with wireless mouse/kb combos not working on usb back 3.0 ports, fine on front 2.0. After months of back and forth with shop, demo's on their computers with my mk320's, and their mk270's Logitech wireless combos, and demo's here at home no joy. They say it's the 2.4Ghz noise...

Combo's work fine on my other 2 win 10 laptops+win7 desktop from a mile away.

Any input on that would be appreciated.

TS
-------------

My real Reason here is to address these errors in the \setupact and setuperr logs:

Are these a Problem?

The same 7 errors starting from original install of windows on 4-12 through today. I've been through dism commands and sfc /scannow many times. I just deleted the old Dism and Cbs, and ran these again:
Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

sfc /scannow

DOS says no problems...


C:\Windows\System32\LogFiles\setupcln and setupact same errors

2021-04-12 18:30:39, Error EnumeratePathEx: FindFirstFile failed for [\\?\C:\$Windows.~BT\*]; GLE = 0x3[gle=0x00000003]
2021-04-12 18:31:21, Error EnumeratePathEx: FindFirstFile failed for [\\?\C:\$WINDOWS.~Q\*]; GLE = 0x3[gle=0x00000003]
2021-04-12 18:31:21, Error EnumeratePathEx: FindFirstFile failed for [\\?\C:\$INPLACE.~TR\*]; GLE = 0x3[gle=0x00000003]
2021-04-12 18:31:21, Error EnumeratePathEx: FindFirstFile failed for [\\?\C:\$Windows.~LS\*]; GLE = 0x3[gle=0x00000003]
2021-04-12 18:31:21, Error EnumeratePathEx: FindFirstFile failed for [\\?\C:\ESD\Windows\*]; GLE = 0x3[gle=0x00000003]
2021-04-12 18:31:21, Error EnumeratePathEx: FindFirstFile failed for [\\?\C:\$Windows.~WS\*]; GLE = 0x3[gle=0x00000003]
2021-04-12 18:31:21, Error EnumeratePathEx: FindFirstFile failed for [\\?\C:\ESD\Download\*];
-----------------------------------------------------------
Here's the DOS window:

DOS
11:50 AM 10/2/2021

Microsoft Windows [Version 10.0.19043.1266]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>Dism /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1266

No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1266

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1266

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Sincerely,
TS

Processor Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz 2.90 GHz
Installed RAM 16.0 GB (15.9 GB usable)
System type 64-bit operating system, x64-based processor
Processor Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz 2.90 GHz
Installed RAM 16.0 GB (15.9 GB usable)
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

- - - Updated - - -

To Whom it may concern,

Re; Logitech wireless mouse keyboard lag, lagging, solved, fixed, repaired.


I moved the win 10 desktop computer to a room with absolutely no other electronics, i.e.: network printer, tv, dvr, router and namely an electric bed, and it worked on all usb ports 2.0 and rear 3.0, I still had to use a 6 inch extension for dongle, on 3.0 but it resolved the problem...

Computer is back in original location, using front usb 2.0 for wireless, but I know it was electronic interference from above mentioned sources that killed the back usb 3.0 wireless connections!

I hope this helps someone else!

Ty,
ts

I'm sill curious about error logs, TIA