Solved repair install

[gregrocker]

No need to remove the bloatware again after a Repair Install. It only reinstalls the OS, but keeps all programs, files and settings in place. If they're not there it's not going to reinstall them.

I don't recommend importing any user settings into a Clean Reinstall, just your User folders which are backed up first.

You can always Repair Install first to see how you like it. It also can be limited by the user settings which might have some corruption that survives.

At any time you can delete D to extend C in Disk mgmt: Partition or Volume - Extend.
I would make my Recovery Disks first so you have a way to restore to factory condition if you ever choose to sell the machine.

 

[drpepper]

I believe I would like to perform the repair install and couple it with deleting/extending the space currently occupied by D: drive first to see how I like the results. Sooner or later I am sure that I will need to be familiar with both repair and clean install of OEM operating systems.

The repair task will have to wait until I get off work tonight or sometime tomorrow. Should I proceed using the tutorial as a guide, or would you like to give further advice before I begin?

drpepper

 

[gregrocker]

It will go smoother if you delete D first in Disk Mgmt, Extend C into the space.
Partition or Volume - Delete
Partition or Volume - Extend

If you haven't yet then I'd also Clean Up Factory Bloatware.

Then run CCleaner Disk and Registry tab followed by Puran Defragger Boot-Time Scan with Full Disk Check, after enabling Intelligent Optimizer on Addtional Operations tab.
CCleaner - Free software downloads and software reviews - CNET Download.com
Puran Defrag Free Edition - Free software downloads and software reviews - CNET Download.com

Now you have a leaner install, cleaned up and organized for the Repair Install

 

[drpepper]

Thanks for the guidance. It looks like I have some more prep work ahead of me. I'm happy I asked.

There are a couple of things I would like to have clarified.

If my understanding is correct, CCleaner is user account specific and will require running it separately on the standard user account and the administrator account. Is that correct?

Exactly where in the sequence of tasks should I create the recovery disks you recommended in an earlier post? Do I need one set of disks for the resale of this computer scenario and another set for my own use if needed later?

drpepper
​

 

[gregrocker]

Just make the Recovery Disks now and save them. You can always copy them later. You'd probably only want them if you sell the computer to add back the bloatware which may add value if the buyer doesn't appreciate a cleaner install and wants all the junk.

Run CCleaner on both accounts to see.

 

[drpepper]

understood ...

I'll post back with success, observations, and/or problems. Unfortunately I don't have the luxury of having the time to follow the steps uninterrupted from start to finish. It may take a day or two. Fortunately there are two other machines I can use if things go foul. -- but -- I am confident that I will not run into problems.

 

[gregrocker]

Take all the time you need. It actually helps discern performance changes as you add Updates and Programs.

I have some installs that are running great that nearly tip over from all of the Updates for Office 2007, so I hold my breath on those.

 

[drpepper]

problems, but first an observation to share with you:
Ccleaner is user account dependent. The three areas I used prior to beginning the attempted repair verified this. Startup programs lists programs for the individual user account. Cleaner and registry in the (sequentially) second account revealed items not addressed in the first one. Maybe this information will prove to be helpful to you in the future.

here are my observations and the order in which the attempted repair progressed:

All preliminary tasks were performed with one hiccup. Deleting D: drive left the unallocated space unavailable for expanding C: drive into the previously occupied disk space. I figured no big deal since the area was not previously available.

Using How to Do a Repair Install to fix Windows 7 as a guide, everything followed the tutorial until step#16. This step was skipped by the process (not by me). My assumption is that the previously configured Internet and network settings were used.

Step#17 found a problem to repair. The error was .NET framework version 4 needs to be repaired. The first attempt displayed downloading 2 updates 0KB total. Something looked wrong with empty updates. The computer rebooted and repeated the process. Upon reboot I had to log into the administrator account, and the repair began where it left off. Curiously, the appearance of the monitor after reboot changed. Instead displaying in the same layout as viewed when performing routine computer tasks, it was a full screen window with no title bar. (I don't know if this is normal or the indicator of a problem.) The same error was displayed again. This time, the repair of .NET appeared to be successful.

Then Windows prepared the desktops to start up. They had to be prepared individually by logging into the user accounts. Both desktops were absent the wallpapers (no big deal). All icons were present and in the proper locations. A review of programs and libraries/folders did not reflect any problems.

It was really late, and I decided to shut down the computer. Why not? The instructions and my observation of the behavior of the computer did not indicate that the repair was still in progress. I figured I could continue later with the last steps because they are to be performed after being confident that all went well. Besides I was concerned because our neighborhood has frequent power interruptions, and I was operating the computer plugged in with the battery removed. I did not want to return to the computer in an off state.

​

Today the computer froze immediately before the login screen on every attempt. (I am posting this via safe mode to avoid having to go form room to room to use different computers.)

)I spent a little time in research. I found that among the tasks performed by .NET framework version 4 are "provides user interface" and "graphic rendering". Trying to tie this in to what Lenovo support had told me (described in the early posts of this thread), I am wondering if a display driver or graphics driver could be the culprit. I include this in hopes that you can tell me if my troubleshooting mindset is correct.

If a driver is not the culprit, I have the following resources available for another repair attempt or clean install and file recovery.

set of recovery discs created in the initial hours of using this compputer when new
set of recovery discs created immediately before attempting the repair install
image backup created by Windows backup and saved to an external drive before creating the second set of recovery discs
the bootable flash drive used for the attempted repair

​

Where do we go from here?

drpepper

​

 

[gregrocker]

If C wouldn't extend into D space then D must have been a Logical partition and requires a second delete of the Logical Volume before becoming Unallocated space. There's not other reason C would not extend if nothing is in the way.

I would Clean Reinstall - Factory OEM Windows 7 to get Win7 unhindered by bloatware.

But I'd first establish a Clean boot to make sure a freeloader isn't causing problems, check the logs and system resources for clues, finish updates and test my hardware if not done yet: Troubleshooting Steps for Windows 7

 

[drpepper]

D:drive did not extend on the first attempt. I deleted it again according to instructions, and it failed to extend on the second attempt also. Prior to the attempted repair I performed the following as outlined in the troubleshooting link you included. I scanned with MSSE, MBAM, and Spybot. I studied Event Viewer and Performance Log before I even started this thread. As limited by my level of understanding, I found nothing which addressed the issue of freezing before log in. I will begin the hardware diagnostics. FYI: I use Speccy periodocally to monitor temperatures. I have not used any temperature monitors which are viewed in the system tray. My research indicates that 60-65C is the upper safe range for the CPU. I have seen CPU and MOBO temps in the 140F (60C) range once (HDD temp). Therefore, I purchased a laptop riser with a cooling fan and tested it by loading it the computer up with processes. I managed to use all but about 200MB of physical memory and use 75-100% of CPU frequency as viewed in Task Manager. The temps rose to around 140F. Returning to normal usage dropped the temps to the 100-105F reange. The internal fan is running. I place my hand near the vent from time to time to check. drpepper How odd! Posting this on the XP machine, preview does not preserve new paragraphs. It merely inserts spaces. What's up with that?

 

[karlsnooks]

Are you using FireFox?

 

[karlsnooks]

I never saw a diskmanagement display.

I'm too lazy to read the entire thread.

Are C and D on the same physical drive? Yes/No

 

[gregrocker]

You're not extending D - you're extending C. You deleted D.

The steps can help gather clues to figure out what the problem is.

You might need to clean out the dust in your laptop: Cleaning Your Laptop Cooling System

 

[drpepper]

Hmm. After struggling with the XP machine not retaining formatting in the last post (yes, using FF on both), I decided to try something one of my friends told me a couple of years ago. Instead of a normal boot sequence I booted in safe mode and restarted. For some reason the boot sequence worked. Subsequent cold boots have worked normally. I don't know why it worked, but it did.

Before shutting down last night no updates were showing to be available. The first successful boot tonight showed updates available. There were a total of 78 updates which took four update sessions to complete. There were a few .NET up-dates included in the group.

I don't know if you were replying to me or karlsnooks. I guess I allowed the preview/edit problems on the XP machine distracted me from details. I apologize for giving the wrong information. To set the record straight, I deleted D: and attempted to extend C:. I intend to use available time this week end to review the troubleshooting steps again and perform the hardware tests. As for cleaning the inside of the machine, I have been thinking about the more cramped space than on a desktop. I clean the desktop about once a year. Maybe I should clean the laptop about once every six months.

I need to break it open anyway. I have found conflicting information about the amount of RAM this machine will accommodate, 8GB or 16GB. (Lenovo says 8GB. Belarc indicates only one of four slots occupied.) A look inside should verify that. In the next few months I am thinking of upgrading to Win7 Pro to run XP Mode and maybe a VM. If I do that I will upgrade memory. I need to get an idea of costs so I can budget the upgrade.

For now I will continue to follow troubleshooting and hardware tests (along with cleaning). If I encounter no more boot issues, I'll let a sleeping dog lie. If problems recur, I will opt for a clean install.

drpepper

 

[drpepper]

gregrocker,

I would like some clarification because I don't know if I can take something out of the context of the Troubleshooting Windows 7 Failure to Start tutorial.

regarding the inability to extend C: into the deleted D:
I am trying to understand the failure to extend as separate from failure to boot. This is the out of context detail. The tutorial addresses both Partition Wizard and Hiren's Boot CD as partition recovery tools, but in the context of "no installation shows for repair", quoted from step#6 of the tutorial.

Is it wise and reasonably safe to attempt to restore D: and attempt to perform the delete D:/extend C: task again?
If so, which of the tools do you recommend for someone like me who is in the learning curve?
Are there special steps or precautions which need to be considered?
​

Thanks for your insight.
drpepper

 

[gregrocker]

To get reliable information about your installed and maximum RAM run Crucial System Scanner software to find out what type of memory is in your computer.

If C won't extend after deleting D then use Partition Wizard to Resize Partition - Video Help.

 

[drpepper]

Partition Wizard is just what the doctor ordered. C: has been expanded from 254GB to 283GB. Now I'll move on to another task.

Thanks

 

[drpepper]

**forgot to include in last post -- Crucial indicates that I can upgrade to 8GB RAM**

To efficiently use my available time, I have been a little out of sequence in the steps. I have saved steps demanding my attention for when I can devote my attention to them. In the information below I have not followed up on Google results because I wanted to provide you with my findings first. I don't know if some of them are blind alleys or not.

tasks performed and observations:

Memtest86+ -- ran 11 passes, no errors found. However, reboot froze before log on again repeatedly.

I had to perform hard shut downs to recover. I had to boot in safe mode and then reboot form safe mode to log on successfully.

Upon log on I had no Internet connection in either the administrator account of the standard user account. Action Center and Windows troubleshooter provided no help. I had to use System Restore to restore to a point from yesterday to establish Internet connection.

​

MBAM and MSSE scans are clean.

Event Viewer (by Category, limited to today or last 24 hours):

CRITICAL -- All events in the last 24 hours are related to the hard shut downs as described above.

ERROR

source: VDS Basic Provider
event ID: 1
task category: none
details: unexpected failure error code D@01010004
found in Google: Try clean boot. I have not done this yet. I am going to wait for your recommendations.

source: kernel event tracer
event ID: 2
task category: session
details: circular kernel context logger failed to start 0xc0000035
found in Google: this link looks like it may be the one to follow windows 7 - Event Viewer: Event ID 2 'Session "Circular Kernel Context Logger" failed to start with the following error: 0xC0000035' - Super User

source: WMI
event ID: 10
task category: session
details: event filter with query ...
found in Google: not sure which one to follow

source: disk
event ID: 10
task category: none
details: driver detected controller error \devices\harddisk\DR1
found in Google: This may be the best link The driver detected a controller error on - Microsoft Answers
​

WARNING

Port Locker -- This is a Lenovo program.
details: installation may be corrupt.

I am wondering if removing and installing this again may be the cure.

​

Please tell me what to ignore and what order to follow up on the others.

Thanks,
drpepper

 

[drpepper]

before I start: I keep forgetting to ask about this. I have not found a click to log out feature on this forum. What am I missing?

update from previous posts:

The tools linked to in Trouble Shooting Windows 7 Failure to Boot > HD Diagnostic > carrona.org. fail to recognize my HDD. I have tried two of the recommended tools, W_D_DLG_504f.iso and SEATOOLS DOS 223ALL.iso with the same results. Both booted and ran successfully from the CDs I burned. Is this an indicator of a serious problem?

EDIT: The Lenovo support web site ran me in circles (as usual). I finally found a quick hard drive test. No problems were found.

 

[gregrocker]

Run WD data Lifeguard extended CD test. WD Support / Downloads / Select Product

Running a Clean Boot is one of the first troubleshooting steps given. What is the delay?

I would seriously consider a Clean Reinstall - Factory OEM Windows 7 to shrug off the Lenovo crapware including useless duplicate utilities that have much better versions built into Win7. You've already shown your chops as a tech enthusiast and I've never met a tech enthusiast who doesn't do this first thing.