Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

Windows Update not working after WinGate 5.2 update

Dec 03 03 6:07 am

I've updated our gateway from WinGate 5.1 to Wingate 5.2
After this update "WindowsUpdate service" was not able to work anymore giving error "0x800A138F" on all machines.

I followed some indications found at http://www.updatexp.com/0x800A138F.html
but with no success.
Any help?

Thanks a lot.
Eros Olmi
Italy

Added Later: Client OS: WinXPPro SP1

Dec 03 03 11:52 am

Have just checked this here. Both XP Pro and XP (with and without SP1a on) updated as expected. However on an XP machine that was an upgrade from Win 2k I received the same error as you. Are your client machines fresh installs of XP or were they a different OS to start with and been upgraded?!

When I then connected this upgraded machine directly to the internet (to take WinGate out of the equation) and ran Windows Update, it still did not work and gave the above error. Could you try connecting your problem machine directly to the internet, and seeing if it worked then?!

Regards

Neil

Dec 03 03 2:18 pm

Just to let you know, i've fixed the problem machine here that was giving the same error code as you. The problem was that the xp client machine had hte wrong date and time (was set to 2001). So this is also something for you to check on your machines.

Regards

Neil

Dec 04 03 5:21 am

Hi Neil.
I tried to connect over standard modem with no lan and WindowsUpdate works fine. Only through Wingate 5.2 it gives error. I've to say that it was working with WinGate 5.1 just 5 min before the upgrade.
Maybe it has something to do with SSL? We use banking software in SSL modem and it works fine on WinGate 5.2. Only Windows Update is not working.
Thanks a lot

Dec 06 03 10:29 am

I had the same problem on two machines (just 5min ago). After deleting the wingate cache and rebuilding the index everything works fine.

regards

Olaf

Dec 09 03 11:10 pm

Thanks Olaf.
Your suggestion solved the problem in my case too.
Maybe Wingate Setup program should delete previous version cache.
I remember also in other updates there were some cache problems.
Thanks a lot.
Eros
Post a reply