Thread: Windows 7 help

Hey everybody I just got windows 7 form a friend yesterday and installed it and it was working fine but also yesterday after the installation was completed I had to update microsoft .net framework 4 so I did then he asked me if I wanted to restart now or later so I did it now it shutdown then while starting up it froze on a screen that configuring something so I left it for about an hour when it did nothing I kept pressing the startup button to shutdown the PC then I opened it again it was working but without the mouse or keyboard so I did the same but opened it in safe mode downloaded and installed their updates then now when I try to open it normally again it get me a blue screen error so now I don't understand anything so my question is :

What Should I do XD


Ps.: I'm currently on safe mode with networking

---------- Post added at 04:43 PM ---------- Previous post was at 04:37 PM ----------



Oh Yeah I tried repairing microsoft .net framework 4 but it didn't work so I tried re-installing it but it needed to uninstall the microsoft .net framework extended before I did the same to client profile so I didn't do it


Leave all the shit above and read this:

I want to know what is the best way to do a clean
re-install for my windows after formatting my PC so how do I format my PC

Do you get a blue screen error as soon as you start your computer? Than the best action you can take is start from scratch and reinstall Windows 7 on your PC. Makes sure that there are no files left on the partition where you want to install your Windows 7. Format the HDD to make sure (Always a good idea when you reinstall windows).

It might not be the answer you where looking for, but this is probably the easiest way to make sure you don't get the same error. When you finished reinstalling make sure you put automatic updates from Windows off. Use that only if you are sure that won't activate the windows activation page where you have 30 days to activate your windows licence.

Have you installed SP1? Maybe try that, or if it fails to solve the problem, try installing SP1, then .net framework.

No need to reinstall just yet. First, as you can't boot into the desktop, the registry backup should still be ok. When you power on, press and hold the "f8" key (or press repeatedly) before you get to the windows logo. On the advanced boot configuration menu (the screen that comes up by pressing f8) select "Last Known Good Configuration" and hit enter, as long as the registry backup is not corrupted, that should get you back into windows.

Failing that, insert the OS cd and boot from it and use the recovery manager to access the startup repair more details here :

System Recovery Options

If both fails, then, and only then resort to a clean install.

I don't know many people who use recovery manager, even high end techs for the reason that a reinstall with a preconfigured answer file takes less time / brain power then fighting with a dead box. If the box is the only Domain Controller with no backup solution, then that is a different thing. if the "last known settings" doesn't work, break out the OS install DVD. Unless you have some really important software that has to be deactivated to untie an user license, you will spend more time at the recovery console manager just figuring out how it works then just reinstalling.

After you get at least as far as being able to access pre windows updates, you should make sure your bios reversion for mainboard is updated. Also, unless you have an application that runs in .net, you don't need the .net framework for normal operations.

Good luck mate!

Originally Posted by tacocoglis

I don't know many people who use recovery manager, even high end techs for the reason that a reinstall with a preconfigured answer file takes less time / brain power then fighting with a dead box. If the box is the only Domain Controller with no backup solution, then that is a different thing. if the "last known settings" doesn't work, break out the OS install DVD. Unless you have some really important software that has to be deactivated to untie an user license, you will spend more time at the recovery console manager just figuring out how it works then just reinstalling.

After you get at least as far as being able to access pre windows updates, you should make sure your bios reversion for mainboard is updated. Also, unless you have an application that runs in .net, you don't need the .net framework for normal operations.

Good luck mate!

I've been in IT for quite a while, never came across minor problems that recovery manager couldn't fix. Besides, windows 7 has a pretty much nearly fully automated recovery, nothing lost by trying. Especially if there's any data to save.

Cheers blitzed :P but basic data can be pulled directly from a hard drive with a 30 dollar sata to USB converter, drives can be swapped around, the old boot partion can be shrinked -> new partion created in the new space -> windows installed on new partion -> data migrated -> old partion deleted -> new spaced extended into the new os partion. Unless it is data that can't be easily replicated into a new environment because of EFS keys on a machine that isn't on a domain, or the machine is the only domain controller on the network.

the system has most likely already gone back to a restore point since that is the default of the OS when an update fails a configuration udpate as mentioned by the OP. System repair may catch a registary glitch after it scans all of the entries - 1 hour's time or progress bar staring with no guarenteed result? If there wasn't a backup, system complete restore won't do the OP much good either. memtest = worthless unless ram is suspected but I wouldn't even go down that path until a reinstall fails. console -> buy a powerball/megamillions ticket :D No one CompTIA'ed would ever try this other than trying to remove a rootkit, recovering from a bad linux dualboot install

I read about a way in which windows can use the recovery console and a serial port attached working computer also in recoveryconsole command mode to test items, but I would have pulled the plug a long time ago on the paticent unless it was a case as stated before.

Peace Yo!

Originally Posted by tacocoglis

Cheers blitzed :P but basic data can be pulled directly from a hard drive with a 30 dollar sata to USB converter, drives can be swapped around, the old boot partion can be shrinked -> new partion created in the new space -> windows installed on new partion -> data migrated -> old partion deleted -> new spaced extended into the new os partion. Unless it is data that can't be easily replicated into a new environment because of EFS keys on a machine that isn't on a domain, or the machine is the only domain controller on the network.

the system has most likely already gone back to a restore point since that is the default of the OS when an update fails a configuration udpate as mentioned by the OP. System repair may catch a registary glitch after it scans all of the entries - 1 hour's time or progress bar staring with no guarenteed result? If there wasn't a backup, system complete restore won't do the OP much good either. memtest = worthless unless ram is suspected but I wouldn't even go down that path until a reinstall fails. console -> buy a powerball/megamillions ticket :D No one CompTIA'ed would ever try this other than trying to remove a rootkit, recovering from a bad linux dualboot install

I read about a way in which windows can use the recovery console and a serial port attached working computer also in recoveryconsole command mode to test items, but I would have pulled the plug a long time ago on the paticent unless it was a case as stated before.

Peace Yo!

I see where you're coming from mate, and i agree with you. Did a lot of in house IT support, home visits etc, and basically did the easy stuff that i could explain to customers, so usually when i advise on something, that same methodology comes up, lol. Which is fast becoming obsolete due to new options with every coming OS.

When windows 7 starts...If the OS is not configured correctly, mass physical memory dumps are created which causes this error....

[Windows update upgrade, fix and also ur configures OS...when it do not update ur OS properly this blue screen error happens....most of the time when updates don't installed serially (Sometimes in windows update u'll see some important updates are not ticked, so we add them), we become the victim of blue screen error]

What to do/ How to fix this....

There are three ways...
1. Easiest way...restore ur windows....
2. If u remember the last updates(all of them) name(probably we don't do, no problemo**), go to windows update and delete/uninstall them. now ur OS should work fine....
**If cant remember the name u'll see the dates in windows updates. remove all of the updates of that date :)
3. Reinstall the windows

Hope this helps...And next time be-careful when u update....I am always available in irc...