clean install windows7 pro will not update and trouble shooters error or hang

NUMBA1TARGET

Honorable
Dec 30, 2013
31
0
10,540
I have installed a dell oem windows7 pro x64 into a dell latitude D630. Windows update searches for updates continuously without ever finding one. It is a clean install with sp1, I know there are updates available. Windows is activated, I can go online, I can download Microsoft security essentials (which updated itself...), I can download windows update trouble shooters (the ones that run to conclusion say either "done" or alternate between saying they fixed things to saying they fixed some things but could not fix another.). Some of the trouble shooters just run till they "checking for updates online..." and hours pass with 75% to 80% of the system ram used and the CPU pulling 46% to 56% load of something. No activity beyond an initial spike on the network and occasional pokes on the HDD which seem like normal windows polling not real activity. I can not figure it out.I even tried the windows 10 upgrade ap to check my system ( it was said it would fix issues automatically and or generate a report.), It hangs the same way, Ram usage and CPU load goes up and nothing happens. Just sits there until I end the process.
update:
The Windows7 pro x64 is reporting the Intel core 2 duo as "architecture: AMD x64.". Is this right?
 
Solution
part of the issue is that system, Dell D630, was not included on the compatible list for Win 7. There were never anyWin 7 drivers issued for that model through dell, ( although there are work arounds like loading the vista drivers in compatibility mode) but it's not surprising that you are having issues with updates. Win 10 would be even worse. Try doing a clean reload and then trying to run updates...
part of the issue is that system, Dell D630, was not included on the compatible list for Win 7. There were never anyWin 7 drivers issued for that model through dell, ( although there are work arounds like loading the vista drivers in compatibility mode) but it's not surprising that you are having issues with updates. Win 10 would be even worse. Try doing a clean reload and then trying to run updates...
 
Solution

NUMBA1TARGET

Honorable
Dec 30, 2013
31
0
10,540


It seems that just using the thing for a time (on if not in use for about 3 days) allowed auto updates in the system and the service to eventually work it out automatically. Suddenly the update indicator appeared on the "shut down" button under the start menu. It has been since updated to win10 professional x64 and runs surprisingly well. I still do not understand the reasons for the initial difficulty with Windows update but, again, it resolved itself after several days trying to auto update. (in an aside, Windows 10 seems scary connected to personal info and the "update others" function enabled by default? Really?).
 

NUMBA1TARGET

Honorable
Dec 30, 2013
31
0
10,540


Copy that windows 10. Bench marks for that particular system were great under win10 but the way it is set up (default privacy/security/update settings) is really unsettling to me and even after reviewing every setting I could learn of I am still not feeling secure/ comfortable with the odd network activity I still see. I can feel advertisers on the fringes searching for my data...(sigh).
 

BrandX

Honorable
Aug 30, 2013
179
0
10,710
Thanks Numba. I'm having a similar issue with a laptop, but mine came installed with Windows 7 Premium and I reinstalled on a new hard drive with a different OEM disk - validated but will not update. I'll see if mine updates by itself.
 

chewible

Honorable
Jan 2, 2014
14
0
10,510
Hi,
I recently spent hours on this issue. I found a fix - from Twizar on youtube. The number of updates is what is hanging your update utility. You have to install KB3135445 update alone - download from Microsoft website.
**But first go to windows update, and turn off automatic updates in settings, as he describes briefly in the video. Then install the stand-alone KB3135445.
After install, I re-ran the update, it took a while which scared me, but it worked.
I had to share this as it drove me nuts without the fix.
Link to video: