OS and Software > Microsoft Help > Win 8 back to Win 7

Win 8 back to Win 7

I think a bit more information here is needed as to what exactly you are looking to do.

The reason I say this is that if you are running Windows 8 x64, and wanted to install Windows 7 x86, that should not be a problem with the hard drive, if you saved all your data to an external source first, and did a clean install of Windows 7.

Maybe its just me, but when I do an install of an OS, I don't like the upgrade or downgrade route. Sure, its a pain as you have to re-install all your applications and restore all your data, but to me, that eliminates a ton of other issues.

So, if you are looking to install Windows 7 x86 on top of an existing Windows 8 x64 install, I would highly suggest if you wanted to do that, to save your data, make sure you have all your application installs, and just start over with Windows 7.

Not saying what you are asking cannot be done, I just feel that it would be less hassle and you could end up with a cleaner, more stable result in the end.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

This isn't a discussion on what I need, it was more on would this issue affect people enough it might be a concern.
Would just deleting the partition be enough then installing. Would this lack of compatibility be of concern, if for instance, yes, the user chose the upgrade/downgrade option?
I myself wouldn't, and would start fresh.

I just feel there is a point of discussion here because of what maybe an install/migration issue.
I could be wrong.

I understand it is only in a boot environment that it comes into play, just curious if anyone has been caught out with the boundaries in place.
--
The only thing necessary for the triumph of evil is for good men to do nothing - Edmund Burke

I totally agree with you on your points. It is an interesting topic for discussion, as there are a lot of people out there that do prefer to do in-place upgrades / downgrades instead of a full format / install of a given OS.

I do not know enough about the subject to comment on it further, so it will be interesting for me, as well as a learning experience to see what others have to say on this subject.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

reply to norwegian
I also recommend doing a full wipe and install.

I have found that unless the previous version of windows was a completely new install, with nothing installed, when you do an in-place upgrade there is ALWAYS something that comes back to bite you.

I have tried upgrades from every version of windows to the next at least once ignoring my own advice and have always regretted it. (Even from win3.1 to 95 to 98)

If the in-place upgrade was able to properly repair the previously installed version of windows first before the upgrade it would probably not be an issue but the upgrade seems to assume that everything is fine and blindly plows ahead.

reply to norwegian

reply to norwegian
BTW win7 can do GPT too.

Every VM I've made for server 2008R2 since esxi 5 is EFI boot with a GPT boot VM disk

I've made a few win 7 vm's like this too.

but win7 will only make a GPT boot drive if its EFI boot not Bios.
--
»www.change.org/petitions/create-···imcity-4

reply to nwrickert

reply to DarkLogix

reply to norwegian
I did this on a Dell laptop that came preloaded with Windows 8.
I disabled the uEFI so it ran in 'regular' BIOS mode..
It would have allowed Windows 7 32 bit / x86 to install if I wanted to...

reply to norwegian
The upgrade Paths the OP laid out are not legit Upgrade/Downgrade paths as you can not change x86 to x64 during a migration.
If you had an Win 7 X86 system and you purchased an Upgrade to Win 8 you would get Win 8 x86 only via download purchase.

Now, there are ways to change to x64 from X86 using an upgrade disk, but they require a fresh OS install and not a system migration. So partitions are not an issue, as they will be deleted and recreated if needed.

The same is true for a downgrade from win 8 to win 7 or back to x86.

Thanks for pointing that out.

I'm trying to figure if there will be any issue with that limitation and will it affect anyone long term.

I've no time for testing my curiosity out like in the past, and hoped someone might have been able to pass on knowledge on the restrictions and if it could be of concern in certain instances.
--
The only thing necessary for the triumph of evil is for good men to do nothing - Edmund Burke

reply to norwegian

reply to norwegian
Just to add to my above comments, if hardware permits, like a second HDD or partition in the PC, the Upgrade may offer to backup your data files, format and install the new OS and then transfer your data back into the new installed OS.
This can even be offered if changing to x64. This migration process is OK but may not handle all your program and there data files, that is it may fail on some that are not supported.
When doing this type of migration there are many more possible errors that could come up and cause problems so most people avoid this method and do a clean install and manually transfer there data files.

So no one can see an issue with this?

Reformat replies really don't discuss this at all, and as I've said already, I am aware of that option, I do it all the time, that is not at discussion.

The partition table and operating system properties are, so please try and discuss this.
--
The only thing necessary for the triumph of evil is for good men to do nothing - Edmund Burke

reply to mmainprize

reply to norwegian
Please excuse the cross post from another site forum, in hopes I can get this discussion happening to help others who "do not know to wipe" etc, or as in this users case, did not wipe at all and kept all data, however risky it might be - especially if nothing is backed up and you try it.

»www.wilderssecurity.com/showthre···t=339321
particularly this entry on one way to resolve it.
»www.wilderssecurity.com/showpost···count=20

Also, for those just starting out and might need to understand more, I found the Microsoft FAQ's a little more helpful.

»msdn.microsoft.com/en-us/library···525.aspx

Hopefully this is worth continuing - and if not I will request it be sent to the hardware forum.
I just thought it would be worthy of discussion for newbies future reference here as it is really specific to Windows than any other platform.
--
The only thing necessary for the triumph of evil is for good men to do nothing - Edmund Burke

reply to norwegian
I think I've found a topic that explorers a little on what I was hoping someone would enlighten me to:

»arstechnica.com/information-tech···know-it/

nwrickert,

Microsoft has clarified its requirements by stating that systems certified for Windows 8 must allow secure boot to enter custom mode or be disabled, but not on systems using the ARM architecture.

I interpret that statement as meaning that authors of UEFI firmware are responsible for making it possible to dual boot operating systems.

So, perhaps the problem you're identifying lies with those manufacturers who don't implement the UEFI standard in the manner specified by Microsoft.

My source:

»en.wikipedia.org/wiki/Unified_Ex···nterface

It's possible I could have misinterpreted what is saw there.

I have a UEFI based system, but it contains no Secure Boot option. It's a self-built system using an ASRock H77M-ITX motherboard running Windows 8 64 bit. I don't dual boot, so I haven't tried that to determine whether it provides the option you speak of.

Just some thoughts on the subject. Additional comments or clarification welcome. This is complicated subject, so it's easy to get wrapped around the axle. Been there, done that.

Freddy