Bug 396276 - MBR Corrupted while after installing
Summary: MBR Corrupted while after installing
Status: RESOLVED DUPLICATE of bug 396444
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Bootloader (show other bugs)
Version: RC 1
Hardware: i386 Windows Vista
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Jozef Uhliarik
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-02 06:41 UTC by Hemant Vankar
Modified: 2008-06-04 14:59 UTC (History)
1 user (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
y2logs (1.71 MB, application/x-compressed-tar)
2008-06-02 08:25 UTC, stefan van ruiten
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hemant Vankar 2008-06-02 06:41:53 UTC
Hi I found my vista MBR corrupted when I installed opensuse 11 RC1. Below is the message I found.



Windows failed to start. A recent hardware or software change might be the cause.

File: \windows\system32\winload.exe
status: 0xc000000e
Info: The selected entry could not be loaded because the application is missing or corrupt
Comment 1 Jiri Srain 2008-06-02 06:47:11 UTC
Please, attach the logs, see http://en.opensuse.org/Bugs/YaST for how to get them. During installation YaST needn't change MBR, however, you should check these settings in the installation proposals.
Comment 2 stefan van ruiten 2008-06-02 08:25:38 UTC
Created attachment 219438 [details]
y2logs
Comment 3 stefan van ruiten 2008-06-02 08:26:46 UTC
hello,

i just did a default x64 opensuse RC1 DVD install on my spare partition next to Vista Ultimate x64 and I have the Exact Same issue. after installation I cannot boot vista anymore with the same error and the same error-code. The problem is not with windows since when I mount the vista drive in suse I can browse just fine to winload.exe

stefan
Comment 4 Jozef Uhliarik 2008-06-04 14:59:22 UTC
it is duplicate of bug #396444

*** This bug has been marked as a duplicate of bug 396444 ***