Microsoft: Windows 7 and Office 2010 Thread
Needs more Lemon Pledge
Joined: Mar 2005
Posts: 52,768
Likes: 2,000
From: Phoenix, AZ
I need to reinstall the OS on a 4 year old W7 machine. Some programs are getting a little funky (looking at you Google Drive...) and it's time for a re-install. No w/10 on this machine, thank you.
Do any of you have a procedure you go through to get the machin eback to the state it was in before the re-install? I already have a list of all the installed programs, but all the little crap like mapping drives, setting custom "favorite" locations in Outlook and explorer, desktop icon layout, Browser stored passwords, etc. are the real pain in the ass.
Anyone have any good methods for getting back to square one but with all your accumulated customizations?
Do any of you have a procedure you go through to get the machin eback to the state it was in before the re-install? I already have a list of all the installed programs, but all the little crap like mapping drives, setting custom "favorite" locations in Outlook and explorer, desktop icon layout, Browser stored passwords, etc. are the real pain in the ass.
Anyone have any good methods for getting back to square one but with all your accumulated customizations?
Needs more Lemon Pledge
Joined: Mar 2005
Posts: 52,768
Likes: 2,000
From: Phoenix, AZ
In your experience, is there anything that it does not transfer over?
things like:
-User created Outlook macros that I made a toolbar button for?
-Pinned folders in the taskbar Explorer icon?
-Favorites in Explorer?
-Network preferences (mapped drives, etc.)?
I am not going to wipe the original drive, just add a larger SSD and install W7 fresh to that, so I will be able to go back and grab what I need (may even VM the old drive temporarily) but I am trying to make this as easy as possible.
things like:
-User created Outlook macros that I made a toolbar button for?
-Pinned folders in the taskbar Explorer icon?
-Favorites in Explorer?
-Network preferences (mapped drives, etc.)?
I am not going to wipe the original drive, just add a larger SSD and install W7 fresh to that, so I will be able to go back and grab what I need (may even VM the old drive temporarily) but I am trying to make this as easy as possible.
_
Joined: Nov 2006
Posts: 19,312
Likes: 3,430
Anyone else experiencing problems updating Win 7 lately?
I was trying to get Win 7 updates for April, but it would hang at the "Checking for updates..." screen. I left it running for like 6 hours and nothing.
HIwmY.png
This wasn't the first time the "Checking for updates..." took a long time either. It's been happening since about October 2015. It took about 3 hours to check for, download, and install the March 2016 updates.
I also noticed that svchost was consuming a lot of RAM and CPU was running at almost 100% because of it.
Anyways, I thought something might have screwed up my Win 7 install, so I decided to reformat and reinstall Win 7 Pro. But same problem after it installs SP1. It just hangs.
I found other people having the same problem here --> Windows 7 SP1 Windows Update stuck checking for updates - Super User
After installing the KB3102810 update as someone suggested in the above post, it finds the updates I need, but it hangs at installing update 93 of 159, so I stop update process, reboot and search for updates again, but it hangs at "Checking for updates..." again.
I reformat and reinstall again following same steps as above (i.e. installing KB3102810 update after SP1). This time, though, I installed the updates in smaller quantities. I select all the updates except for those that were released in 2015 (around 90 of them). All updates install successfully. But when I check for Win updates again, it hangs at "Checking for updates..." screen. I even left it running overnight for about 6 hours again, and nothing. Just hangs.
I've reformatted and reinstalled Win 7 Pro like 8 times already this weekend (lost count after 5th install) and no matter what I do, I cannot get all the updates that I need installed.
Not a conspiracy theorist, but I'm starting to believe what others have said, that Microsoft is trying to get people to upgrade to Win 10 by purposely not letting us update Win 7, or at least making it take a long time.
I was trying to get Win 7 updates for April, but it would hang at the "Checking for updates..." screen. I left it running for like 6 hours and nothing.
HIwmY.png
This wasn't the first time the "Checking for updates..." took a long time either. It's been happening since about October 2015. It took about 3 hours to check for, download, and install the March 2016 updates.
I also noticed that svchost was consuming a lot of RAM and CPU was running at almost 100% because of it.
Anyways, I thought something might have screwed up my Win 7 install, so I decided to reformat and reinstall Win 7 Pro. But same problem after it installs SP1. It just hangs.
I found other people having the same problem here --> Windows 7 SP1 Windows Update stuck checking for updates - Super User
After installing the KB3102810 update as someone suggested in the above post, it finds the updates I need, but it hangs at installing update 93 of 159, so I stop update process, reboot and search for updates again, but it hangs at "Checking for updates..." again.
I reformat and reinstall again following same steps as above (i.e. installing KB3102810 update after SP1). This time, though, I installed the updates in smaller quantities. I select all the updates except for those that were released in 2015 (around 90 of them). All updates install successfully. But when I check for Win updates again, it hangs at "Checking for updates..." screen. I even left it running overnight for about 6 hours again, and nothing. Just hangs.
I've reformatted and reinstalled Win 7 Pro like 8 times already this weekend (lost count after 5th install) and no matter what I do, I cannot get all the updates that I need installed.
Not a conspiracy theorist, but I'm starting to believe what others have said, that Microsoft is trying to get people to upgrade to Win 10 by purposely not letting us update Win 7, or at least making it take a long time.
Last edited by AZuser; Apr 17, 2016 at 06:43 PM.
Thread Starter
Sanest Florida Man
Joined: Aug 2007
Posts: 46,006
Likes: 11,782
From: Florida
Anyone else experiencing problems updating Win 7 lately?
I was trying to get Win 7 updates for April, but it would hang at the "Checking for updates..." screen. I left it running for like 6 hours and nothing.
This wasn't the first time the "Checking for updates..." took a long time either. It's been happening since about October 2015. It took about 3 hours to check for, download, and install the March 2016 updates.
I also noticed that svchost was consuming a lot of RAM and CPU was running at almost 100% because of it.
Anyways, I thought something might have screwed up my Win 7 install, so I decided to reformat and reinstall Win 7 Pro. But same problem after it installs SP1. It just hangs.
I found other people having the same problem here --> Windows 7 SP1 Windows Update stuck checking for updates - Super User
After installing the KB3102810 update as someone suggested in the above post, it finds the updates I need, but it hangs at installing update 93 of 159, so I stop update process, reboot and search for updates again, but it hangs at "Checking for updates..." again.
I reformat and reinstall again following same steps as above (i.e. installing KB3102810 update after SP1). This time, though, I installed the updates in smaller quantities. I select all the updates except for those that were released in 2015 (around 90 of them). All updates install successfully. But when I check for Win updates again, it hangs at "Checking for updates..." screen. I even left it running overnight for about 6 hours again, and nothing. Just hangs.
I've reformatted and reinstalled Win 7 Pro like 8 times already this weekend (lost count after 5th install) and no matter what I do, I cannot get all the updates that I need installed.
Not a conspiracy theorist, but I'm starting to believe what others have said, that Microsoft is trying to get people to upgrade to Win 10 by purposely not letting us update Win 7, or at least making it take a long time.
I was trying to get Win 7 updates for April, but it would hang at the "Checking for updates..." screen. I left it running for like 6 hours and nothing.
This wasn't the first time the "Checking for updates..." took a long time either. It's been happening since about October 2015. It took about 3 hours to check for, download, and install the March 2016 updates.
I also noticed that svchost was consuming a lot of RAM and CPU was running at almost 100% because of it.
Anyways, I thought something might have screwed up my Win 7 install, so I decided to reformat and reinstall Win 7 Pro. But same problem after it installs SP1. It just hangs.
I found other people having the same problem here --> Windows 7 SP1 Windows Update stuck checking for updates - Super User
After installing the KB3102810 update as someone suggested in the above post, it finds the updates I need, but it hangs at installing update 93 of 159, so I stop update process, reboot and search for updates again, but it hangs at "Checking for updates..." again.
I reformat and reinstall again following same steps as above (i.e. installing KB3102810 update after SP1). This time, though, I installed the updates in smaller quantities. I select all the updates except for those that were released in 2015 (around 90 of them). All updates install successfully. But when I check for Win updates again, it hangs at "Checking for updates..." screen. I even left it running overnight for about 6 hours again, and nothing. Just hangs.
I've reformatted and reinstalled Win 7 Pro like 8 times already this weekend (lost count after 5th install) and no matter what I do, I cannot get all the updates that I need installed.
Not a conspiracy theorist, but I'm starting to believe what others have said, that Microsoft is trying to get people to upgrade to Win 10 by purposely not letting us update Win 7, or at least making it take a long time.
I've been dealing with the same shit with POS stations for my client. I had to reinstall the OS on a bunch of POS stations and then run updates. Everyone hung on getting updates, so I found the KB3102810 patch ran that and sometimes it would be decent at getting updates but other times it would still take 1+ hrs before the updates showed up. They eventually did but it was annoying.
Needs more Lemon Pledge
Joined: Mar 2005
Posts: 52,768
Likes: 2,000
From: Phoenix, AZ
Senior Moderator
Joined: Apr 2010
Posts: 48,302
Likes: 9,173
From: SoCal, CA
end of "mainstream" support was last year, they're pushing through 2020 for 'extended' support
_
Joined: Nov 2006
Posts: 19,312
Likes: 3,430
Bruh, you got an HP!?
I've been dealing with the same shit with POS stations for my client. I had to reinstall the OS on a bunch of POS stations and then run updates. Everyone hung on getting updates, so I found the KB3102810 patch ran that and sometimes it would be decent at getting updates but other times it would still take 1+ hrs before the updates showed up. They eventually did but it was annoying.
I've been dealing with the same shit with POS stations for my client. I had to reinstall the OS on a bunch of POS stations and then run updates. Everyone hung on getting updates, so I found the KB3102810 patch ran that and sometimes it would be decent at getting updates but other times it would still take 1+ hrs before the updates showed up. They eventually did but it was annoying.
It's a Toshiba laptop. Didn't have this problem the last time when I replaced the HDD and installed Win 7. Very weird.
Needs more Lemon Pledge
Joined: Mar 2005
Posts: 52,768
Likes: 2,000
From: Phoenix, AZ
I think the MS gods like you better!
Having said that, my re-install machine greeted this AM with 160 important updates. Installing now...
Got the case for the new build yesterday, all the guts should arrive today.
Having said that, my re-install machine greeted this AM with 160 important updates. Installing now...
Got the case for the new build yesterday, all the guts should arrive today.
Thread Starter
Sanest Florida Man
Joined: Aug 2007
Posts: 46,006
Likes: 11,782
From: Florida
Microsoft released a “convenience rollup” update that includes all updates to 7 SP1 up until April 2016 in one update file so you don’t need to download 200 updates every time. You can also slipstream this convenience rollup into an ISO. Going forward they will be doing monthly rollup updates
x86
http://download.windowsupdate.com/d/...b0a74b2cbd.msu
x64
http://download.windowsupdate.com/d/...1264cd93b9.msu
https://blogs.technet.microsoft.com/...ows-7-and-8-1/
x86
http://download.windowsupdate.com/d/...b0a74b2cbd.msu
x64
http://download.windowsupdate.com/d/...1264cd93b9.msu
https://blogs.technet.microsoft.com/...ows-7-and-8-1/
_
Joined: Nov 2006
Posts: 19,312
Likes: 3,430
Win 7 now too?
Another quality update from Microsoft.
https://www.zdnet.com/article/micros...t-genuine-pcs/
Another quality update from Microsoft.
https://www.zdnet.com/article/micros...t-genuine-pcs/
Microsoft's killer Windows 7 patch: Breaks networking, flags legit PCs as 'Not genuine'
Windows sysadmins wake up on Wednesday with an almighty Patch Tuesday headache.
January 10, 2019
Some Windows 7 admins are feeling the pain of Microsoft's latest updates in this week's Patch Tuesday releases.
Thankfully for Microsoft, hardworking admins continue to spot bugs that it didn't detect during pre-release testing.
This time they've found that its January security updates are bricking Windows 7 devices with an errant 'Not Genuine' Windows license error, and a bug that blocks administrator access to remote shares on Windows Server 2008 R2 and Windows 7.
The issues stem from the Monthly Rollup update, KB4480970, and the security-only update, KB4480960, for Windows 7 SP1 and Windows Server 2008 R2 SP1.
. . . .
Regarding the 'Not Genuine' Windows 7 error, Microsoft confirms that "some users are reporting the KMS Activation error, 'Not Genuine', 0xc004f200 on Windows 7 devices".
"We are aware of this incident and are presently investigating it. We will provide an update when available," writes Microsoft on both KB4480960 and KB4480970.The source of the activation error is an eight-month-old update for Microsoft's anti-piracy Windows Activation Technologies, the same tech that recently caused panic after deactivating legitimate copies of Windows 10.
As noted by AskWoody.com, Microsoft for some reason this week pushed the April update, KB971033, which was meant to help "confirm that the copy of Windows 7 that is running on your computer is genuine".
The problem, as one sleuthing sysadmin concluded on Reddit, is that KB971033 should never have been installed in a KMS environment. The sysadmin discovered the cause while fixing several thousand Windows 7 virtual desktops that suddenly and wrongly reported they were running non-genuine Windows.
"Woke up this morning to find a few thousand Windows 7 VDI machines reporting that Windows 7 wasn't genuine. After much troubleshooting we found that KB971033 (should not have been installed in a KMS environment in the first place) was installed on these machines," the sysadmin wrote.
. . . .
[ SNIP ]
Windows sysadmins wake up on Wednesday with an almighty Patch Tuesday headache.
January 10, 2019
Some Windows 7 admins are feeling the pain of Microsoft's latest updates in this week's Patch Tuesday releases.
Thankfully for Microsoft, hardworking admins continue to spot bugs that it didn't detect during pre-release testing.
This time they've found that its January security updates are bricking Windows 7 devices with an errant 'Not Genuine' Windows license error, and a bug that blocks administrator access to remote shares on Windows Server 2008 R2 and Windows 7.
The issues stem from the Monthly Rollup update, KB4480970, and the security-only update, KB4480960, for Windows 7 SP1 and Windows Server 2008 R2 SP1.
. . . .
Regarding the 'Not Genuine' Windows 7 error, Microsoft confirms that "some users are reporting the KMS Activation error, 'Not Genuine', 0xc004f200 on Windows 7 devices".
"We are aware of this incident and are presently investigating it. We will provide an update when available," writes Microsoft on both KB4480960 and KB4480970.The source of the activation error is an eight-month-old update for Microsoft's anti-piracy Windows Activation Technologies, the same tech that recently caused panic after deactivating legitimate copies of Windows 10.
As noted by AskWoody.com, Microsoft for some reason this week pushed the April update, KB971033, which was meant to help "confirm that the copy of Windows 7 that is running on your computer is genuine".
The problem, as one sleuthing sysadmin concluded on Reddit, is that KB971033 should never have been installed in a KMS environment. The sysadmin discovered the cause while fixing several thousand Windows 7 virtual desktops that suddenly and wrongly reported they were running non-genuine Windows.
"Woke up this morning to find a few thousand Windows 7 VDI machines reporting that Windows 7 wasn't genuine. After much troubleshooting we found that KB971033 (should not have been installed in a KMS environment in the first place) was installed on these machines," the sysadmin wrote.
. . . .
[ SNIP ]
Needs more Lemon Pledge
Joined: Mar 2005
Posts: 52,768
Likes: 2,000
From: Phoenix, AZ
Anyone else having a tough time with W7 machines after the latest monthly patches? Basically it totally jammed up my RDP use (I log into them form across the room).
I just uninstalled them from one machine and suffered through nearly an hour of no-boot-at-all for the "reboot" after uninstalling. Nothing, Zip Nada. Finally pulled the plug from the box and let it sit for a few, then plugged it back in and it seems to have booted OK. Will have to test out the RDP to see if the problems persist.
I just uninstalled them from one machine and suffered through nearly an hour of no-boot-at-all for the "reboot" after uninstalling. Nothing, Zip Nada. Finally pulled the plug from the box and let it sit for a few, then plugged it back in and it seems to have booted OK. Will have to test out the RDP to see if the problems persist.
Needs more Lemon Pledge
Joined: Mar 2005
Posts: 52,768
Likes: 2,000
From: Phoenix, AZ
Using RealVNC for now, dunno what made this start all of a sudden.
Race Director
Joined: Dec 2003
Posts: 12,521
Likes: 1,824
From: MAGA country
^^^^ so no change in the issue after uninstalling the latest security update??
I don't use RDP so not totally familiar. Do you have the limit on simultaneous log ins set to 1 on the target machine? If so, increase it to 2 and see if you can log in with the new account...
If you can now log in with the new account, then that pretty much tells you the issue is the failure of the original log in to "log out".
I don't use RDP so not totally familiar. Do you have the limit on simultaneous log ins set to 1 on the target machine? If so, increase it to 2 and see if you can log in with the new account...
If you can now log in with the new account, then that pretty much tells you the issue is the failure of the original log in to "log out".
I heard it costs $135 to update 7 or 8 to 10 (if you didn't do the free upgrade several years ago).
I found a cnet article that showed me how to update it for free. Did it yesterday. I are happy.
I found a cnet article that showed me how to update it for free. Did it yesterday. I are happy.