[RESOLVED] WUA issues following update to 2.6

TomTom · November 21, 2024 - 8:37 AM

Hello everyone,

I've already mentioned this on Discord, so I'm posting here as well.

Since the WAPT update to version 2.6, our clients are no longer able to check for Windows updates. They remain stuck in a "needs scan" status, but when we run the scan manually, we see the task start and then stop instantly.

Oddly enough, I managed to force a scan on my test machine after several restarts, but it's not deploying the patches correctly. I should mention that I haven't changed any approvals since the update.

Thank you.

jlepiquet · November 21, 2024 - 12:17

Hello,

this is a known bug on our end. The private/cache folder does not exist.

You need to deploy a package (either a new version of an existing one or a completely new package) to the machines.
Then the WUA scan should work.

Regards,

TomTom · November 21, 2024 - 2:18 PM

Yes, I did restart the scan after updating/installing a package.

However, on a clean Windows 10 machine, the system isn't showing all the updates I've approved since the WAPT update to v2.6.
It won't deploy certain KBs...

jlepiquet · November 21, 2024 - 3:47 PM

Are these older KBs?
They might be included in the new Cumulative releases and therefore installed through that KB.

TomTom · November 21, 2024 - 3:59 PM

No, I'm sure because Windows LAPS isn't active on my test machine after the update attempts, and that's because the KB article enabling its use isn't installed on the client machine.
Again, the day before the WAPT update, I configured two client machines that installed their updates without any problems. So, for me, there's a connection with version 2.6...

jlepiquet · November 21, 2024 - 4:06 PM

Can you provide us with screenshots?

TomTom · November 22, 2024 - 8:57 AM

Of course.
There is one copy of the authorized updates on the server, and the other two are copies from two test machines. The first shows the updates deployed on one machine before the WAPT update, and the second shows the updates deployed on a second machine after the server was upgraded to version 2.6.

: 2024-11-21_17h19_01.png (140.12 KB) Viewed 12619 times

: 2024-11-21_17h22_41.png (62.31 KB) Viewed 12619 times

: 2024-11-21_17h26_18.png (41.5 KiB) Viewed 12619 times

jlepiquet · November 25, 2024 - 11:02 AM

Hi Thomas,

I'm a bit stuck, could you contact me at the office so we can watch live?

Best regards,

Joeffrey

TomTom · November 27, 2024 - 8:39 AM

Hello Joeffrey,

could we find some time to make progress on this?

It's becoming very disruptive to my daily life.

Thank you,
Thomas

TomTom · November 27, 2024 - 09:38

Okay, I'm going to look into this a bit more.

The update I was talking about regarding Windows LAPS activation is KB5025221, but it's not in my repository despite scanning the machines that should be requesting it.
So, it seems the problem lies there.
My test is based on a clean version 22h2 of Windows 10. No matter which PC I'm working on, none of them are reporting this KB.
Yet, again, before I decided to deploy WAPT 2.6, it was definitely there...

Is it possible to completely clean the update repository? Could it be that the local Windows Update scan isn't transferring all update requests since 2.6?