New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quectel WWAN driver always found again even after installing it #59
Comments
Hi, to troubleshoot problem 1, please run For problem 2, that package uses
which is an (older) official Microsoft tool, and there is some documentation around it. For example this website explains what the return codes mean. You are getting If the information in the above link is correct this would mean 34 drivers were added to Windows successfully, but none of them could directly be used for a connected device. I think it could be possible that the drivers are installed but not used because they aren't really applicable to your machine. Maybe this is a similar problem to problem 1, where a package is being mis-detected. If you could run Thanks! |
LSUDEBUG1_20SY.txt Hi Jantari, Thanks! Just added both DEBUG logs:) |
Matching device HardwareIDs with wildcards was added in f59ea57 and e4e28bc, but maybe mistakenly so. HardwareIDs can contain * when I thought it was a wildcard added by Lenovo https://learn.microsoft.com/en-us/windows-hardware/drivers/install/generic-identifiers
I have had some time to look into this and have a few ideas on what could be the cause of it, but have to do more testing to verify. I also identified the same issue in some logfiles from model 20X1 deployments with a similar Quectel WWAN driver |
Great, thank you! Just let me know if i can help here anyhow. |
So, I had an idea how to fix this and implemented it in dbee40c but I couldn't validate the fix on any 20X3 anymore because Lenovo has superseded the package that originally exhibited the problem for me with a newer version that works differently and doesn't have the issue anymore. However I just realized I could manually download the old package and add it to an offline repository to test the fix and it did work, so I can likely include this in the next release of LSUClient. Do your problem cases still reproduce the same as they did when you opened the issue or were your packages updated as well? |
I could compare the results from the current release 1.5.0 vs develop on a 21C5 today with the exact driver package 1.5.0 results:
develop-branch results as of d595dcb:
with |
Published Version 1.5.1 which includes this fix |
Version
1.5.0
Computer Model
See Problem
Problem
Hi jantari,
First of, thanks for releasing the 1.5.0 Version. Just implemented it to our Pilot Group!
Unfortunately, i have two other Problems (also had it on the previous Version).
Problem 1: It seems, that some Drivers want to install themself on every check again (we tried reebots and shutdowns on these machines).
Problem 2: Some Chipset Device Software Drivers will not be installed.
Our Script we scheduling while after a login:
Problem1:
DEVICE 1 Model: 21C8S0MX00
Freitag, 4. November 2022 10:30:49
Proxy :
ProxyCredential :
ProxyUseDefaultCredential : False
MaxExternalDetectionRuntime : 00:10:00
MaxExtractRuntime : 00:20:00
MaxInstallerRuntime : 00:20:00
AUSFÜHRLICH: Processing package 'r1yfu05w - Quectel EM05-G Wireless WAN Driver - 10 (20H2 or Later)/11 (21H2 or Later)'
AUSFÜHRLICH: Installing package r1yfu05w ...
ID : r1yfu05w
Title : Quectel EM05-G Wireless WAN Driver - 10 (20H2 or Later)/11 (21H2 or Later)
Type : Driver
Success : True
FailureReason :
PendingAction : REBOOT_SUGGESTED
ExitCode : 0
StandardOutput : {}
StandardError : {}
LogOutput : {}
Runtime : 00:00:01.3362134
Freitag, 11. November 2022 06:59:58
Proxy :
ProxyCredential :
ProxyUseDefaultCredential : False
MaxExternalDetectionRuntime : 00:10:00
MaxExtractRuntime : 00:20:00
MaxInstallerRuntime : 00:20:00
AUSFÜHRLICH: Processing package 'r1yfu05w - Quectel EM05-G Wireless WAN Driver - 10 (20H2 or Later)/11 (21H2 or Later)'
AUSFÜHRLICH: Installing package r1yfu05w ...
ID : r1yfu05w
Title : Quectel EM05-G Wireless WAN Driver - 10 (20H2 or Later)/11 (21H2 or Later)
Type : Driver
Success : True
FailureReason :
PendingAction : REBOOT_SUGGESTED
ExitCode : 0
StandardOutput : {}
StandardError : {}
LogOutput : {}
Runtime : 00:00:02.1884399
Montag, 14. November 2022 07:06:43
Proxy :
ProxyCredential :
ProxyUseDefaultCredential : False
MaxExternalDetectionRuntime : 00:10:00
MaxExtractRuntime : 00:20:00
MaxInstallerRuntime : 00:20:00
AUSFÜHRLICH: Processing package 'r1yfu05w - Quectel EM05-G Wireless WAN Driver - 10 (20H2 or Later)/11 (21H2 or Later)'
AUSFÜHRLICH: Installing package r1yfu05w ...
ID : r1yfu05w
Title : Quectel EM05-G Wireless WAN Driver - 10 (20H2 or Later)/11 (21H2 or Later)
Type : Driver
Success : True
FailureReason :
PendingAction : REBOOT_SUGGESTED
ExitCode : 0
StandardOutput : {}
StandardError : {}
LogOutput : {}
Runtime : 00:00:01.3805968
Montag, 26. September 2022 08:12:08
AUSFÜHRLICH: Processing package 'n24au05w - Realtek Audio Driver - 10 (1809 or Later)/11 (21H2 or Later)'
AUSFÜHRLICH: Starting download of 'https://download.lenovo.com/pccbbs/mobiles/n24au05w.txt'
AUSFÜHRLICH: Installing package n24au05w ...
ID : n24au05w
Title : Realtek Audio Driver - 10 (1809 or Later)/11 (21H2 or Later)
Type : Driver
Success : True
FailureReason :
PendingAction : REBOOT_SUGGESTED
ExitCode : 259
StandardOutput : {}
StandardError : {}
LogOutput : {}
Runtime : 00:00:18.1586815
Device 2 Model: Mdl20L6SBLF00
Freitag, 11. November 2022 06:47:12
Proxy :
ProxyCredential :
ProxyUseDefaultCredential : False
MaxExternalDetectionRuntime : 00:10:00
MaxExtractRuntime : 00:20:00
MaxInstallerRuntime : 00:20:00
AUSFÜHRLICH: Processing package 'n24au05w - Realtek Audio Driver - 10 (1809 or Later)/11 (21H2 or Later)'
AUSFÜHRLICH: Starting download of 'https://download.lenovo.com/pccbbs/mobiles/n24au05w.txt'
AUSFÜHRLICH: Installing package n24au05w ...
ID : n24au05w
Title : Realtek Audio Driver - 10 (1809 or Later)/11 (21H2 or Later)
Type : Driver
Success : True
FailureReason :
PendingAction : REBOOT_SUGGESTED
ExitCode : 259
StandardOutput : {}
StandardError : {}
LogOutput : {}
Runtime : 00:00:16.6687355
Montag, 14. November 2022 07:00:56
Proxy :
ProxyCredential :
ProxyUseDefaultCredential : False
MaxExternalDetectionRuntime : 00:10:00
MaxExtractRuntime : 00:20:00
MaxInstallerRuntime : 00:20:00
AUSFÜHRLICH: Processing package 'n24au05w - Realtek Audio Driver - 10 (1809 or Later)/11 (21H2 or Later)'
AUSFÜHRLICH: Starting download of 'https://download.lenovo.com/pccbbs/mobiles/n24au05w.txt'
AUSFÜHRLICH: Installing package n24au05w ...
ID : n24au05w
Title : Realtek Audio Driver - 10 (1809 or Later)/11 (21H2 or Later)
Type : Driver
Success : True
FailureReason :
PendingAction : REBOOT_SUGGESTED
ExitCode : 259
StandardOutput : {}
StandardError : {}
LogOutput : {}
Runtime : 00:00:16.5505164
Problem 2
Model: Mdl20SYS3C802
Montag, 14. November 2022 06:46:28
Proxy :
ProxyCredential :
ProxyUseDefaultCredential : False
MaxExternalDetectionRuntime : 00:10:00
MaxExtractRuntime : 00:20:00
MaxInstallerRuntime : 00:20:00
Ausnahme beim Aufrufen von "DownloadFile" mit 2 Argument(en): "Der Remoteserver hat einen Fehler zurückgegeben: (404)
Nicht gefunden."
In C:\Program Files\WindowsPowerShell\Modules\LSUClient\private\Save-PackageFile.ps1:46 Zeichen:9
Ausnahme beim Aufrufen von "DownloadFile" mit 2 Argument(en): "Der Remoteserver hat einen Fehler zurückgegeben: (404)
Nicht gefunden."
In C:\Program Files\WindowsPowerShell\Modules\LSUClient\private\Save-PackageFile.ps1:46 Zeichen:9
WARNUNG: The command or file '%PACKAGEPATH%\tbtfwdetect26_dch.exe 8' could not be found from 'C:\Windows\TEMP\djjy5s5b.crl\lpctmp1o.qkw' and was not run
AUSFÜHRLICH: Processing package 'n2uic02w - Intel Chipset Device Softwar - 10 (1909 or Later)/11 (21H2 or Later)'
AUSFÜHRLICH: Starting download of 'https://download.lenovo.com/pccbbs/mobiles/n2uic02w.txt'
AUSFÜHRLICH: Installing package n2uic02w ...
ID : n2uic02w
Title : Intel Chipset Device Softwar - 10 (1909 or Later)/11 (21H2 or Later)
Type : Driver
Success : False
FailureReason : INSTALLER_EXITCODE
PendingAction : NONE
ExitCode : 13312
StandardOutput : {}
StandardError : {}
LogOutput : {}
Runtime : 00:00:03.7725961
Thanks for your Time here!
Additional context
No response
The text was updated successfully, but these errors were encountered: