W10 running messed up with a W7 restoration... ?

Hi,

Here's the context :

I had a W10 enterprise X64 22H2 19045.2965 really not giving me what I expected compared to my previous W7 utlimate in terms of fluidity and response time so I decided 2 days ago to restore a 2 years old &µ@X£#*§ macrium image of it : this image was taken from the exact same disk housing at times 1 win7 partition & the boot menu for 1 W10 pro partition installed on another (still in place) disk.

Everything went well. Ok, I was wrong NOT to backup the previous MBR/boot menu/etc... before, but mscong to point to the correct actual w10 entry now on the same disk wasn't tough.

Getting back to 10, as I couldn't get winamp to run, closing as soon as I hit play (I'm designing a new modern skin), I thought of some kind of bug and came to install a fresh copy of it, to get
"this system is out of date, winamp 592 requires windows 7 sp1 or higher"... In the meantime everything like youtube or browsing did eat up to 80% or more of an I7 950/24Go RAM...

I tried a repair by shift-clic restart => brief check, got back, no change.
Tried to put on it a fresh W10 copy by launching the .iso setup from my W10 desktop, choosing to keep files & applications => CPU usage has reduced to standard values but I still get "out of date OS" when trying to install anything.

By the way, W7 is up.

What went wrong ?

I came to w10 as I've lost eyesight 2 years ago from a rampaging glaucoma because of w7 unable to manage black text on white backgrounds in some parts that windowblinds was unable to manage with dark skins, to find almost the same parts in w10, fortunately in few cases solved by dark mode.

I've tried w11, plaggued with the exact same non dark mode parts. Thanks microsoft for a really well done job.

Anyway, I'd be very happy NOT to have to install again a fresh w10 copy alongside of applications/configuration/etc...


Does somebody has a clue ?

After much digging it is much worse than expected as going thru disk manager I got reminded what slips in my mind when choosing the destination disl for w7 restoration, my pc has 4 disks with W7 & 10 on separate disks, meann that I don't understand WHY restoring this old image messed up my w10.

Something in the boot manager ? in the boot menu files ?



- - - Updated - - -

What puzzles me is the "good health (startup, swap file, 'memory image after incident', main partition) for the C: disk, W10 one.

What puzzles me is the "good health (startup, swap file, 'memory image after incident', main partition) for the C: disk, W10 one.

- - - Updated - - -

Megahertz said:

Again, In what can we help you?

From disk manager, you're booting to disk 0 - System partition and transferring the boot sequence to drive 3 - partition C: that is label as Win 10. It seems you're booting into Win 10. Are you?
Does drive 3 has win 10? Open a CMD window and type: winver

Indeed, that's what happens and I'm writing this comment IN w10.
When booting I'm presented with a 2 entries boot menu
1 - windows 10 (disk 3 - C:)
2 - windows 7 (disk 0 - now G:)

w10 is pro version for workstation 22H2 19045.2965.

I just don't understand why and how restoring an image file to disk 0 has made disk 3 less than it was before with w10 NOT recognized as it is, leaving me with applications installation stopping after telling me that my system doesn't meet the requirements, that I must have windows 7 SP1 or higher to complete successfully their installation when BEFORE this restoration I could install just what I'd have wanted.

As I really do appreciate your effort to help me, it would greatly improve the conversation if you'd read what I did publish on the subject.
Let me summarize it to you.

0. PC with 4 disks.
1. Win7 ultimate on disk 0, win10 PRO on disk 2.
2. Win7 macrium imaged 3 years ago.
3. Modification of win10 : pro => workstation, disk 2 => disk 3.
4. win10 unsatisfaction => win7 restoration on disk 0.
|
|=> image => old configuration (disk 0, disk 2) => msconfig to modify w10 files disk2 => disk3 for the boot menu
|
|=> win10 messed up : CPU usage +++, applications installation IN w10 = "OS not meeting requirements, need w7 SP1 or higher". For all aplications I've tried, even basic ones as winrar.

Is that clear enough ?


I've tried :
1. Shift-restart/repair => no luck.
2. upgrade so called not w10 workstation 22H2 to w10 workstation 22H2 from desktop, keeping files/applications => CPU usage solved. Still getting "OS out of date".
3. Tried repair, booting from ISO => no luck.
4. Did SFC /scannox => nothing to report.

eventviewer => nothing special besides a recurring error on a COM file.