Open AxiteYT opened 1 year ago
I'm also experiencing this issue when downgrading to version 7.1.8, I'm wondering if maybe Dell has changed something on their end.
I am having Same issue. If I go straight to the url that is presented in software it downloads just fine. Any luck on chasing this down?
None as of yet as far as using the package, I ended up creating a custom package which has worked out well as an interim solution
I had similar issue before updating DAT to 7.1.9 Previously, DAT was not handling properly drivers packed as EXE So DAT was downloading an EXE and tried to extract it as if it was an archive.
From what I know, 7.1.9 fixed that for me
Unfortunately neither version has been working for me.
I had the same issue with OptiPlex 7000. I download the .EXE and manually and put it in the driver download folder for the Dell model followed by a re-run of the tool. The tool was able to find the file and continue extracting and creating the package as normal. So hopefully you can use that workaround until the issue is fixed.
I just experienced the same with 7.1.9 downloading the Lenovo P16 gen 1 drivers. As @hillihappo mentioned, manually downloading the .exe driver pack from Lenovo's site and re-running DAT allowed the .exe to extract as normal.
Same issue for me, here are the logs for when it attempts to download the Dell Precision 5820. Issue is consistent for 7.1.9, 7.20, & 7.2.1.
- ConfigMgr: Latest driver revision found - A16 DriverAutomationTool 12/23/2022 10:35:08 AM 18580 (0x4894)
- ConfigMgr: Checking ConfigMgr for driver packages matching - Drivers - Dell Precision 5820 Tower - Windows 10 x64 DriverAutomationTool 12/23/2022 10:35:08 AM 18580 (0x4894)
- Adding details to summary output DriverAutomationTool 12/23/2022 10:35:08 AM 18580 (0x4894)
- ConfigMgr: New driver package detected - Processing DriverAutomationTool 12/23/2022 10:35:08 AM 18580 (0x4894)
- ConfigMgr: Creating Precision 5820 Tower download folder DriverAutomationTool 12/23/2022 10:35:08 AM 18580 (0x4894)
- ConfigMgr: Downloading Precision-5820-Tower-KGH4P_Win10_1.0_A16.exe DriverAutomationTool 12/23/2022 10:35:08 AM 18580 (0x4894)
- ConfigMgr: Downloading from URL: https://dl.dell.com/FOLDER09179576M/1/Precision-5820-Tower-KGH4P_Win10_1.0_A16.exe DriverAutomationTool 12/23/2022 10:35:08 AM 18580 (0x4894)
- BitsTransfer: Checking BITS background job DriverAutomationTool 12/23/2022 10:35:14 AM 18580 (0x4894)
- BitTransfer: Job state is "Error Transferred Transferred Transferred Transferring" DriverAutomationTool 12/23/2022 10:35:14 AM 18580 (0x4894)
- BitTransfer: File size - 2845000016 2845000016 2845000016 2845000016 2845000016 DriverAutomationTool 12/23/2022 10:35:14 AM 18580 (0x4894)
======== Errors(s) Occurred ======== DriverAutomationTool 12/23/2022 10:35:14 AM 18580 (0x4894)
[Error] - Method invocation failed because [System.Object[]] does not contain a method named 'op_Division'. DriverAutomationTool 12/23/2022 10:35:14 AM 18580 (0x4894)
DriverAutomationTool 12/23/2022 10:35:14 AM 18580 (0x4894)
- BitsTransfer: Checking BITS background job DriverAutomationTool 12/23/2022 10:35:14 AM 18580 (0x4894)
- BitTransfer: Job state is "Error Transferred Transferred Transferred Transferring" DriverAutomationTool 12/23/2022 10:35:15 AM 18580 (0x4894)
- BitTransfer: File size - 2845000016 2845000016 2845000016 2845000016 2845000016 DriverAutomationTool 12/23/2022 10:35:15 AM 18580 (0x4894)
======== Errors(s) Occurred ======== DriverAutomationTool 12/23/2022 10:35:15 AM 18580 (0x4894)
[Error] - Method invocation failed because [System.Object[]] does not contain a method named 'op_Division'. DriverAutomationTool 12/23/2022 10:35:15 AM 18580 (0x4894)
DriverAutomationTool 12/23/2022 10:35:15 AM 18580 (0x4894)
- BitsTransfer: Checking BITS background job DriverAutomationTool 12/23/2022 10:35:15 AM 18580 (0x4894)
- BitTransfer: Job state is "Error Transferred Transferred Transferred Transferring" DriverAutomationTool 12/23/2022 10:35:15 AM 18580 (0x4894)
- BitTransfer: File size - 2845000016 2845000016 2845000016 2845000016 2845000016 DriverAutomationTool 12/23/2022 10:35:15 AM 18580 (0x4894)
I am also seeing this error for multiple Dell models when trying to download Windows 11 drivers. This particular chunk is for the 5510 download but I have seen it for other models as well. I have also tried versions 7.1.9, 7.2.0, and 7.2.1:
Error] - Method invocation failed because [System.Object[]] does not contain a method named 'op_Division'.]LOG]!><time="08:45:57.786 -300" date="01-04-2023" component="DriverAutomationTool" type="3" thread="10916" file="">
<![LOG[ ]LOG]!><time="08:45:57.817 -300" date="01-04-2023" component="DriverAutomationTool" type="3" thread="10916" file="">
<![LOG[- BitsTransfer: Checking BITS background job]LOG]!><time="08:45:57.926 -300" date="01-04-2023" component="DriverAutomationTool" type="1" thread="10916" file="">
<![LOG[- BitTransfer: Job state is "Transferring Transferring Transferring"]LOG]!><time="08:45:58.114 -300" date="01-04-2023" component="DriverAutomationTool" type="1" thread="10916" file="">
<![LOG[- BitTransfer: File size - 2325132960 2325132960 2325132960]LOG]!><time="08:45:58.239 -300" date="01-04-2023" component="DriverAutomationTool" type="1" thread="10916" file="">
I've had a similar issue as well looks related to #450 as well. I think its related to DAT not cleaning up stuck or failed BIT Transfers.
Job state is "Transferred Transferred Transferring" Looking at the powershell suggests that its pulling in multiple BIT Transfer jobs with the same name and then its crashing when trying to see how those jobs are doing as its not expecting there to be more than one...
To check this i ran Get-BitsTransfer -AllUsers
on the machine i use for DAT (powershell as admin) and it listed 4 or 5 JobIDs with the display name "Latitude 5430-DriverDownload"
I then ran Get-BitsTransfer -AllUser | Remove-BitsTransfer to remove the Jobs and tried DAT again. This time it downloaded and packaged fine.
Not 100% sure the best way to implement this as a permanent fix maybe using the JobID instead of DisplayName or clearing out the Job queues on load... But for now i'm going to manually check the Get-BitsTransfer -AllUser
before setting DAT going...
This doesn't seem to resolve anything for me.
When I look in the temp download location, I see directories:
..\Dell\Latitude 5420\Driver Cab[RandomText].tmp
This file has the same file size as the completed EXE or CAB. I should have probably renamed the file to see if that worked, but instead I just deleted it and replaced it with the files download manually. Then after rebooting and restarting DAT and driver downloads, it completes successfully.
Until a fix is found for this, I'm just maintaining a cache of the CABs that error out in a directory structure I can drop in before running DAT.
Version: 7.1.9
Hi there, when downloading certain Dell Driver Packs, please find examples below:
Latitude 7390 Windows 10 A16 x64 Driver Pack:
Dell Latitude 7430 A01 Windows 10 x64 Driver Pack: