New
#1
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 ?