F5F Stay Refreshed Software Operating Systems Issue with Windows Update (does not function)

Issue with Windows Update (does not function)

Issue with Windows Update (does not function)

R
Rizzex
Member
54
02-06-2016, 09:25 AM
#1
Hi I experience issues with WU on a Win10 pro x64 PC running 2004. The last updates were done 10 days ago (Sept 5th), mostly Ms Office stuff and a few others. Win10 was updated to 2004 on Aug 28th. Now when I try to update manually I get the following error message: "We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet." I made sure I'm connected to the internet. I also have plenty of disk space (142GB available). Except from WU, everything seems to work well. I tried googling this issue and found some advice but nothing seems to solve my problem. Any advice/idea? Thank you very much in advance for your help. best, -a-
R
Rizzex
02-06-2016, 09:25 AM #1

Hi I experience issues with WU on a Win10 pro x64 PC running 2004. The last updates were done 10 days ago (Sept 5th), mostly Ms Office stuff and a few others. Win10 was updated to 2004 on Aug 28th. Now when I try to update manually I get the following error message: "We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet." I made sure I'm connected to the internet. I also have plenty of disk space (142GB available). Except from WU, everything seems to work well. I tried googling this issue and found some advice but nothing seems to solve my problem. Any advice/idea? Thank you very much in advance for your help. best, -a-

O
Oma_
Member
68
02-07-2016, 03:57 AM
#2
Thanks for letting me know. The update didn’t help, so here’s another idea. Please let me know if you’d like more options. Appreciate your patience.
O
Oma_
02-07-2016, 03:57 AM #2

Thanks for letting me know. The update didn’t help, so here’s another idea. Please let me know if you’d like more options. Appreciate your patience.

T
194
02-13-2016, 02:43 PM
#3
Sure thing! Everything looks good. You're quick to respond, which is great. I'll confirm the details right away—just let me know if you need anything else. Thanks!
T
ThiLellesGames
02-13-2016, 02:43 PM #3

Sure thing! Everything looks good. You're quick to respond, which is great. I'll confirm the details right away—just let me know if you need anything else. Thanks!

L
l2p_Robinhudi
Member
67
02-14-2016, 02:28 AM
#4
I turned off IPV6 and restarted -> WU didn't function properly even after that. I tried doing it remotely, which prevented me from checking what was happening while CheckDisk was running. Is there a log file saved somewhere? Anyway, the login screen reappeared quickly, so it seems CheckDisk wasn't much of an issue. After running checkdisk, no errors or corruption were detected. Wow! I just noticed you made this video to help me. You're really great. The symptoms remain unchanged. I'm now applying Windows updates using the media creation tool again. Looking forward to seeing it! Thanks a lot! -a-
L
l2p_Robinhudi
02-14-2016, 02:28 AM #4

I turned off IPV6 and restarted -> WU didn't function properly even after that. I tried doing it remotely, which prevented me from checking what was happening while CheckDisk was running. Is there a log file saved somewhere? Anyway, the login screen reappeared quickly, so it seems CheckDisk wasn't much of an issue. After running checkdisk, no errors or corruption were detected. Wow! I just noticed you made this video to help me. You're really great. The symptoms remain unchanged. I'm now applying Windows updates using the media creation tool again. Looking forward to seeing it! Thanks a lot! -a-

T
Thiago8PvP
Junior Member
33
02-14-2016, 03:38 AM
#5
I’ll spend a lot of time reviewing everything and let you know if anything helps. Upgrading or updating via MCT2004.exe didn’t fix the issue. Usually I treat that as planB on most desktops to skip troubleshooting. On this machine, though... Several apps need a lot of changes, and I might not have the install files. I’ll have to check that carefully. That’s definitely something I’m considering. I know I often say it, but I mean it. Thanks.
T
Thiago8PvP
02-14-2016, 03:38 AM #5

I’ll spend a lot of time reviewing everything and let you know if anything helps. Upgrading or updating via MCT2004.exe didn’t fix the issue. Usually I treat that as planB on most desktops to skip troubleshooting. On this machine, though... Several apps need a lot of changes, and I might not have the install files. I’ll have to check that carefully. That’s definitely something I’m considering. I know I often say it, but I mean it. Thanks.

A
alexTNT377
Junior Member
49
02-24-2016, 07:12 AM
#6
It seems the system auto-installed 2004, but you’re questioning whether it was forced. There’s no clear sign they pushed it everywhere yet, as previous issues caused delays.
A
alexTNT377
02-24-2016, 07:12 AM #6

It seems the system auto-installed 2004, but you’re questioning whether it was forced. There’s no clear sign they pushed it everywhere yet, as previous issues caused delays.

T
TryHardMikel
Member
172
02-24-2016, 03:56 PM
#7
2004 was an available choice on WU for a while. I chose the update on August 28th after testing it on several similar PCs without issues. The upgrade proceeded smoothly and WU functioned normally until September 5th (last known updates in WU history). I didn’t manually push the upgrade to 2004 using the Windows upgrade assistant until September 16th (refer to post #3). Still, since this machine was already running 2004, I’m unsure what exactly WUA did.
T
TryHardMikel
02-24-2016, 03:56 PM #7

2004 was an available choice on WU for a while. I chose the update on August 28th after testing it on several similar PCs without issues. The upgrade proceeded smoothly and WU functioned normally until September 5th (last known updates in WU history). I didn’t manually push the upgrade to 2004 using the Windows upgrade assistant until September 16th (refer to post #3). Still, since this machine was already running 2004, I’m unsure what exactly WUA did.

M
MichlLp
Junior Member
6
02-24-2016, 05:09 PM
#8
If I were you, I’d just restore and reinstall everything. It seems like something went wrong completely. On the other hand, you could attempt the reset feature in Windows 10—it offers a chance to preserve your files, though you’ll need to reinstall the software. This might actually resolve the issue.
M
MichlLp
02-24-2016, 05:09 PM #8

If I were you, I’d just restore and reinstall everything. It seems like something went wrong completely. On the other hand, you could attempt the reset feature in Windows 10—it offers a chance to preserve your files, though you’ll need to reinstall the software. This might actually resolve the issue.

N
NightmareAura
Junior Member
15
02-26-2016, 12:32 AM
#9
It looks like your issue might be linked to Office 2016. I checked another Windows 10 2004 machine and reviewed the update log. I installed updates after September 5th from the Microsoft Update Catalog. The first update was for .NET Framework, then a cumulative update for Windows 10 2004. There were several Word updates, but the latest one was about Word itself. When I tried to download it as a .cab file, I couldn't install it. I opened Word to check if an update could be applied there, but got a license error. I then reinstalled Office 2016, but it also failed with an error. It seems the problem is getting worse—PlanB might be the solution.
N
NightmareAura
02-26-2016, 12:32 AM #9

It looks like your issue might be linked to Office 2016. I checked another Windows 10 2004 machine and reviewed the update log. I installed updates after September 5th from the Microsoft Update Catalog. The first update was for .NET Framework, then a cumulative update for Windows 10 2004. There were several Word updates, but the latest one was about Word itself. When I tried to download it as a .cab file, I couldn't install it. I opened Word to check if an update could be applied there, but got a license error. I then reinstalled Office 2016, but it also failed with an error. It seems the problem is getting worse—PlanB might be the solution.