Category: windows

Grub Rescue – error with Windows 7 and Ubuntu

So you have installed a dual boot windows 7 and Ubuntu and then after a futile attempt to make things work at office, decide to delete the partition onto which Ubuntu has been installed. you restart and bang!

GrubRescue>
GrubRescue>
GrubRescue>
GrubRescue>
GrubRescue>
You realize that you need to get things fixed without formatting the hard disk and loosing your windows files.
Here are the steps which I took that worked for me.
1. Boot with a regular windows 7 CD.
Select the English (or your language option)/ keyboard setup etc and click next
3. select “Repair Windows” option
4. after the installation of windows is found, select the install and click next.
5. select the Repair boot option
now if this does not work. You need to get your hands dirty.
6. Select the option of “Command Prompt”
7. Enter the following command
bootsect /nt60 sys c:
this should repair the mbr
incase this does not work try the next option

bcdedit /export C:BCD_Backup

C:

CD Boot

Attrib bcd –s –h –r

ren c:bootbcd bcd.old

bootrec /RebuildBcd

then it said

“Scanning all disks for windows installations.

Please wait, since this may take a while…

Successfully scanned windows installations: 1

[1] C:windows

Add installations to boot list? Yes(y)/No(N)/All(A) : “

I pressed ‘Y’ as there was only one instance of windows installation. Then it said The operation completed successfully.

6. Next entred the following command bootrec /fixmbr It said The operation completed successfully.

7. Next entred the following command bootrec /FixBoot Again It said The operation completed successfully.


incase this does not work try the next option


go to c:

type Dir

if you get a blank directory then thats the problem. Find out what drive letter has been assigned to the primary windows installation drive. in my case, the rescue drive setup by toshiba assigned c to itself. and my windows was loaded onto what dos assumed was D: so i changed the bootsect command a bit

type :

bootsect /nt60 sys d:


and bang!

Windows boots up!


thanks to www.pcchimp.com for this support

and http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/42d3f550-bf5f-459d-94ed-4cbadd7c933c

#Windows7 – #ZeroDay Bug

In a security advisory , Microsoft acknowledged that a bug in SMB (Server Message Block), a Microsoft-made network file- and print-sharing protocol, could be used by attackers to cripple Windows 7 and Windows Server 2008 R2 machines.

The zero-day vulnerability was first reported by Canadian researcher Laurent Gaffie last Wednesday, when he revealed the bug and posted proof-of-concept attack code to the Full Disclosure security mailing list and his blog. According to Gaffie, exploiting the flaw crashes Windows 7 and Server 2008 R2 systems so thoroughly that the only recourse is to manually power off the computers.

At the time, Microsoft only said it was investigating Gaffie’s reports.

Then on Friday, it took the next step and issued the advisory. “Microsoft is aware of public, detailed exploit code that would cause a system to stop functioning or become unreliable,” Dave Forstrom, a spokesman for Microsoft security group, said in an e-mail. “The company is not aware of attacks to exploit the reported vulnerability at this time.”

Forstrom echoed Gaffie’s comments earlier in the week that while an exploit could incapacitate a PC, the vulnerability could not be used by hackers to install malicious code on a Windows 7 system.

Both SMBv1 and its successor, SMBv2, contain the bug. “Windows Vista, Windows Server 2008, Windows XP, Windows Server 2003 and Windows 2000 are not affected,” assured Forstrom.

Attacks could be aimed at any browser, not just Internet Explorer (IE), Microsoft warned. After tricking users into visiting a malicious site or a previously-compromised domain, hackers could feed them specially-crafted URIs (uniform resource identifier), and then crash their PCs with malformed SMB packets.

Microsoft said it may patch the problem, but didn’t spell out a timetable or commit to an out-of-cycle update before the next regularly-scheduled Patch Tuesday of Dec. 8. Instead, the company suggested users block TCP ports 139 and 445 at the firewall. Doing so, however, would disable browsers as well as a host of critical services, including network file-sharing and IT group policies.

Gaffie’s vulnerability was the first zero-day reported and confirmed by Microsoft in Windows 7 since the new operating system went on sale Oct. 22.