Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - vidockq

Pages: [1]
Hello Andrew,

The only error we get in PatchMyPc.log is the following:
Component: Worker
Thread ID: 6
Entry: An error occurred while updating a package in SCCM: Object variable or With block variable not set. [System.NullReferenceException]

We saw the error poping in the notification mail sent when publishing occurs.
The latest one was today.

This is for ConfigMgr Applications only, with the settings Update exisitng applications metadata,deployment type... (Default)

We have had this error "Object variable or With block variable not set." appear on multiple applications in the past 3 weeks.
We had to delete the application and then redeploy it to fix it.

Can you help us with more information in regards to this error?

Thank you for your help. Amazing support!

You are correct, after investigation, the users that experienced this problem are tied to Zoom installations on the user profile.
We found that most links in mails to install zoom will install on user profiles instead of system-wide.

If there is this limitation that it cannot be updated by a Software Update, then the only course that we see if to have an application with detection for
C:\Users\USERNAME\AppData\Roaming\Zoom\uninstall\Installer.exe, removal of it, and pushing the system-wide application instead.

Is there any way this could be incorporated into your scripts also? We already are working on something like this and we could share our scripts.


It seems that Detection rules for Zoom Meeting might not catch the correct version.
We have deployed Zoom Meetings as application and Updates.

As you can see in the attached picture, we have an older version installed (default installation) but there is a new version out as application but no updates come.

After talking to local support to reproduce the result, it seems that only our Dell fleet has this and its due to Driver indeed.
Thank you, it can be closed.


We recently enabled 3rd Party Updates for Visual C++ 2015-2019 Redistributable (x64 x86) on Windows 10 workstations.
In our tests, on 2 new deployed workstations on Windows 10 Build 2004, we got both detected as needing the update and thus the product was installed.

In both cases, the workstations were clean windows 10 images without any installed updates.

Since Windows 10 doesn't have any Visual C++ runtimes pre-installed, could you please investigate the detection rules for it?

Pages: [1]