rollback from win 10

On what windows 7 if so then you have slic marker in bios but not full slic

 

Did you right click and run as admin.

But seeing the loader is working it would bring it up anyway.

 

loader would only install oem:slp key and certificate if he had Full Slic 2.1 in bios it cannot actually install the loader on unsupported partition
i,e, gpt partition.

 

I never asked about the drive being MBR or GPT.

I have always thought that if the loader was run the SLIC Tool Kit would give a false reading.

It did sound to me as the loader was doing it's job. This would mean the drive was MBR ?

You see bobthejoiner these guys know what they are talking about. I just wing it along and hope for the best..

 

You need to login to view this posts content.

 

That is for Windows XP..

No need to worry about that.

For me I would like to see the result of the SLIC Tool Kit ran in a totally fresh install. With NO loader ran.. But that's just me..

 

I have only bought of the shelf motherboards.
Like the one I am using right now.
Asus Sabertooth Z77. not the newest of boards but has served me well since new.

When I first got it I had already flashed many a board with a modded BIOS.
The BIOS now holds SLP and SLIC2.1.

SLP is for Win XP. We wont worry about XP ANY MORE

I have in My Asus board Asus SLIC2.1. I marry that to an Asus CERT and KEY and for all tense and purpose my board is exactly the same a shop bought Asus machine.

I make an OEM install image so when Win 7 installs it is a legit as any official Asus machine.

What my understanding is of Daz's loader this emulates the SLIC2.1 in the BIOS some how. When there is no SLIC2.1 in the BIOS. How it does this I have never bothered to find out.

I would put money on that is how your machine was activated when you got it. Without you knowing.

 

Same here but whole point is loader will not install on unsupported partition i,e, gpt partition. or sometimes manufacturer recovery partitions can effect loader and bob you can try posting links for the moment like example h t tp://i60.tinypic .com/neet74.png we can remove spaces to get to your link. i'm still confused slic is validated so you are saying.

 

@ tnx if his machine was activated with loader originally when windows 10 installed it would have overwritten mbr so loader would have been lost when rolling back to windows 7. whole point is we are lacking info perhaps an MGADiag report is needed.

 

Right. I never knew that bit. Of course...

I understand folk updating their machines from Win 7/8 but I really do think this should be done on a different HDD\SDD to their main OS.
Get a spare HDD, install in this case Win 7, use the loader if you have to. Do the Win 10 upgrade. M.Soft then have your hardware ID on their servers.
Then do a fresh install of Win 10 on this spare HDD. Check if it does activate.
Use it for a bit, test your fav, most used software.
Then if you find out you dont like it just plug in the original HDD.
No messed up system, files or owt else.

In this scenario I personally would not be happy to have updated to Win 10 then back dating to Win 7.
I would feel the need, a desperate need to do a fresh install of Win 7 and get back to normal.
Again, using the loader if needed.

I most definatly would have backed up all my important files before starting owt.

We can definatly help the OP to find a good clean Win 7 image. Well any OS image actually here on the forums.

 

I just made an acronis image of my system partition before I updated, but before that I had been testing on vmware.

 

Yep

Personally. I don't like those image making apps. Not saying they are bad or owt. Just not for me.

As for VM, never used owt like that.

The OP could try both.

 

You need to login to view this posts content.