Issues with Windows 7 identifier

[lincer556]

Hello guys!
Well this is kinda odd since my pc has no problems but i need to repair this kind of CRITICAL mistake, because is not an error...

Thing goes like this, i've cloned my drive from a 160gb disk to a 320 one with XXCLONE utility, and since then, Windows has a strange boot, my Windows work on spanish and the boot is in english...

The problem is the next, i know that to fix this, i need to repair boot or something like it, but here's were it comes trouble and makes all the mistakes, the Windows identifier under BOOT sequence is broken, need to show you a picture of the 'Boot' section of msconfig for you guys to understand me

As you can see, the identifier is broken because is says "Windows 7 x64 () 298.09GiB" and i know that this need's to say "Windows 7 x64 (Professional)" the issues of this mismatch on the identifier is that i cannot do any type Repair/Upgrade install with the Windows 7 disk, the same used to install the system... And also i cannot repair the system because the mismatch...

Windows works, but if i have any type of problem on the system, i cannot repair it....

Please guys, i need help for correcting this ''Clone'' Windows issue, and thanks!

 

[Britton30]

Make sure the 160GB drive is not connected to the PC and try it. Also...
This may help, run the steps outlined in this tutorial, Option Two, and reboot the system:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html#post14392
If that doesn't correct the issue, run it two or more times with a reboot between.
You may get this result:

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log
The system file repair changes will take effect after the next reboot.

Or a message that no integrity violations were found.
Or that Windows Resource Protection found errors it cannot repair, if so rerun the steps above.

 

[Brink]

Hello Lincer,

That is only the name listed in the "Windows Boot Manager" screen at boot. It's not what is used to identify the OS.

Instead, the registry location below is what is used to ID the OS.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion


​

If you like, the tutorial below can help show you how to change this OS name displayed in msconfig and "Windows Boot Manager" to what you like instead.

http://www.sevenforums.com/tutorials/5110-dual-boot-change-os-name-windows-boot-manager.html
​

Hope this helps,
Shawn

 

[lincer556]

Make sure the 160GB drive is not connected to the PC and try it. Also...
This may help, run the steps outlined in this tutorial, Option Two, and reboot the system:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html#post14392
If that doesn't correct the issue, run it two or more times with a reboot between.
You may get this result:

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log
The system file repair changes will take effect after the next reboot.

Or a message that no integrity violations were found.
Or that Windows Resource Protection found errors it cannot repair, if so rerun the steps above.

View attachment 258801

Already tried the CBS last night with no good results, actually sorry for the foreign language, it says "Current Operating System, Default Operating System"

Hello Lincer,

That is only the name listed in the "Windows Boot Manager" screen at boot. It's not what is used to identify the OS.

Instead, the registry location below is what is used to ID the OS.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

View attachment 258878
​

If you like, the tutorial below can help show you how to change this OS name displayed in msconfig and "Windows Boot Manager" to what you like instead.

http://www.sevenforums.com/tutorials/5110-dual-boot-change-os-name-windows-boot-manager.html
​

Hope this helps,
Shawn

Gonna try this one Shawn!

EDIT: I've found another issue, while trying to perform a ''Repair Install'' the Windows 7 compatibility report it says the next:

Translated it's quite simple:
-Cannot update from a Windows version of 64 bits to another from 32 bits. For update, get a 64 bits version of the install disk of Windows or check this website to see how to install Windows 7 without losing Files and Configs (Ps. nothing intresting here)

This is driving me nuts, i've tried to fix files with the sfc and repair the identifier, but nothing seems to work...

Sorry for crappy quality, basically this is the Windows 7 DVD at boot and trying to repair system, but mostly it's like the same as que "Compatibility Report" at the repair install...

Needless to say, that this is the same DVD that installed my Windows 7 unto my PC.

 

[gregrocker]

Are you using a 64 bit Installation DVD or System Repair Disk to try the repairs? The screenshot shows you are in boot mode which probably means you're trying to run Startup Repair or SFC /SCANNOW Run in Command Prompt at Boot , not a Repair Install which is run from the desktop. I would run both.

 

[lincer556]

Are you using a 64 bit Installation DVD or System Repair Disk to try the repairs? The screenshot shows you are in boot mode which probably means you're trying to run Startup Repair or SFC /SCANNOW Run in Command Prompt at Boot , not a Repair Install which is run from the desktop. I would run both.

Thing is, i cannot make any type of repair, nor going to DVD boot and execute SFC or Startup Repair, and not even Repair Install... There's something on my system that is badly broke, the PC works, i can use it, but i need to repair this before having any kind of trouble wich if i had, wouldn't be able to repair since i can't execute the system repair tools.

 

[Brink]

Lincer,

We need to know if you are booting from a 32-bit or 64-bit DVD.

The error you are getting is basically saying that you must boot from a 64-bit DVD instead.