Skip to content
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

Method invocation failed because [System.Object] does not contain a method named 'op_Division' #492

Open
Leedsy1990 opened this issue Jul 15, 2023 · 1 comment

Comments

@Leedsy1990
Copy link

This has started happening this evening when I attempting to download drivers, running the MSI installed version 7.2.1,

I have tried clearing the temp folder as the app suggests in the info tip, and even tried uninstalling the program and reinstalling it but the problem persists. I have been able to download another package successfully as you can see in the attached log file, but now I can't download any more drivers. The server has recently rebooted for windows updates, however everything I can find online for the error in the subject suggests this is related to the powershell script.

image

DriverAutomationTool.log

Please help, I have just deleted all of our old mess of 2000+ drivers from SCCM with the hope of using DAT as our new driver management tool, and thus far not having the best of luck.

@ATDMare
Copy link

ATDMare commented Jul 20, 2023

We noticed similar issues under #450 (comment)

I found that clearing out the stuck BIT Transfers before running DAT seems to help and not had the issue for a while now.

Powershell (as admin):
Get-BitsTransfer -AllUsers | Remove-BitsTransfer

You can see if you have any stuck by just running the first bit.
Get-BitsTransfer -AllUsers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants