[14 janvier 2020] Update list GDR pour Windows 7 SP1 x86/x64 (Fr-En-De-Es-It)

[Thiersee]

@rhahgleuhargh & @pennsylvaniaron

Just as hint, in case you want to work with ADK on the autounattended.xml from Windows Answer File Generator:

you will get a syntax error from ADK if you load the autounattended.xml!

There is a bug I emailed today to the HomePage, you should a line to the top:

Wrong

<!--*************************************************
Windows 10 Answer File Generator
Created using Windows AFG found at:
;http://www.windowsafg.com

Installation Notes
Location: 
Notes: Enter your comments here...
**************************************************-->

<?xml version="1.0" encoding="utf-8"?>

Right

<?xml version="1.0" encoding="utf-8"?>
<!--*************************************************
Windows 10 Answer File Generator
Created using Windows AFG found at:
;http://www.windowsafg.com

Installation Notes
Location: 
Notes: Enter your comments here...
**************************************************-->

As I said, on loading the answer-file in ADK!

20 hours ago, pennsylvaniaron said:

I have an activated win 7 home premium machine in my basement. I'll change the HD and install win 10 home. Theoretically it should activate with a digital license

I'm not sure it will activate, but you can generate a GenuineTicket.xml and activate with it.

Instructions (from point 3. to 5.)

Spoiler

Instructions:

1. Optional: Validate your copy of Windows 7 SP1 or Windows 8.x
2. Install all necessary drivers e.g. ethernet & wireless card
3. Open your Windows 10 ISO and extract gatherosstate.exe from the sources folder to your desktop
4. Run gatherosstate.exe and wait for the GenuineTicket.xml file to be created
5. Copy the GenuineTicket.xml to a USB thumb drive or something
6. Boot to your Windows 10 USB or DVD and perform a fresh install
7. Disable your internet connection
8. Copy GenuineTicket.xml to C:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket\ and then reboot
9. Connect online and you should be activated

Then detach the Win7 HDD, attach a new HDD or SSD and install Win10 (point 6.).

Now follow point 7., 8., 9.

W10 is activated.

Edited September 3, 2019 by Thiersee

[pennsylvaniaron]

RESULTS are in! EUREKA!

First I would like to thank Liam, Thiersee and  RHAHGLEUHARGH for their time and efforts replying and trying to figure this out. I needed to do my method first and see if what I have been reading about Win 10 activation is true. If it didnt work then I was going to try their methods one by one.

I had been experimenting with this with Oracle's VM on a hard drive in my main machine with win 10 installed. In this environment win 10 would not activate at ALL!  I had tried a clean install with a plain jane win 10 home iso, then a slipstreamed win 10 iso. No good on clean installs. I then installed and activated win 7 on the VM and both those iso's also would NOT activate. That did not make sense at all!

I then went to a totally different machine that was activated with win 7. I put in new HD and used the plain jane win 10 iso, did a clean install and activation failed with no product key found. I then hooked up original win 7 hd and cloned it with trueimage and used that HD for the following:

I used the plain jane win 10 iso from within win 7 and did an upgrade to win 10. It ACTIVATED with digital license! I then rebooted with the plain jane win 10 disk and deleted all partitions, did a clean install and it once again ACTIVATED!!

Lastly I used the slipstreamed win 10 home disk I made with the WTK autounattend file with the s/n TX9XD-98N7V-6WMQ6-BX7FG-H8Q99. I formatted the partitions (don't think the following results would be affected) and I got the activation error I had been getting with the VM that s/n TX9XD-98N7V-6WMQ6-BX7FG-H8Q99 cannot be activated and to contact my organization network operator (or something along those lines). I then went to troubleshoot in that same activation page and it said that a digital license had been found for this computer. It provided a box to click on that said activate windows. I clicked on that and BINGO, win 10 activated with a digital license. 

This proved to me what I had read for the last few years that once a computer (and most of the existing hardware) is activated with a qualifying product such as win 7 or win 8 then you can legally upgrade to win 10 (of the same persuasion home, pro etc). This goes even if an individual were to use a non approved method of win 7,8 activation such as a loader or MTK. once a computer is activated it should have no issues activating win 10. I don't understand the reason the autounattend file initially gave an error in activation. The autounattend file has autoactivation skipped and the s/n is only used (supposedly) to get win 10 installed. but the M$ servers knew the hardware was activated once before with a digital license.

At this point it seems that my slipstreamed disk should work on any qualifying microsoft product. In fact someone just dropped off a formally activated win 7 machine (for repair) that has been upgraded to win 10. I will install a new hd and try the same method(s) on this machine also. will report back...

regards....

[pennsylvaniaron]

Just completed same scenario as above with a clients machine. I cloned their HD with trueimage and used the cloned drive for the experiment. I booted with the slipstreamed disk. This disk which I didnt mention before was made with WTK v.1708 including the autounattend file. I got the updates from the msfn forum. In the setup I deleted all the partitions and created new ones. This machine has a UEFI bios. The install went exactly like before. I was asked 3 questions about KB layout and eventually the desktop appeared with all the files and updates I slipstreamed in. Again activation gave me the same error about that home s/n. I clicked on troubleshoot and it found a digital license.

MISSION ACCOMPLISHED!

regards....

[pennsylvaniaron]

ok going to put this to bed. After successfully activating win 10 from steps above I decided to try again on my VM AGAIN. I wasn't sure if I tried the troubleshooting activation built into win 10 the first time I started this journey. Well it didn't work. For some reason "I" cant activate Win 10 on a VM even after having win 7 installed prior. Its no big deal. The VM will be used for testing tweaks, and new cumulative updates etc.

regards...

 

[pennsylvaniaron]

another issue has arisen while experimenting with the WTK and win10 slipstream. In WTK we all make our own personal tweaks to setup win10 as we like it so we do not have to do those tedious tasks later on (as we do in win 7). here is my issue. I use the autounattend file in conjunction with the tweaks in WTK. I have a username (my last name) in the autounattend file to initially setup win 10 for its first boot.

I am using the win10 iso as a universal install disk for "others". I therefore have to add a new account (or user) and in win 10 I ALWAYS setup a new user with a local account as administrator. Once that is done I then can sign out of my last name account and sign into the new local account. Then I can delete my lastname account (and all its files). At this point it is now a 1 user account,  setup for the new user. However once I do that then all the tweaks are gone that I setup for my lastname account when I created this "universal" win10 iso. Win10 has the option of just changing the name of the account but if you do that the account name under USERS in file explorer does NOT change. I do not see how I can change that name. If I can change that name then problem solved. If not>>>

Is there anyway to PRESERVE the tweaks? As an example I set this pc on the desktop, show all items on taskbar, control panel on desktop to name a few.

regards...

 

[pennsylvaniaron]

1 hour ago, pennsylvaniaron said:

another issue has arisen while experimenting with the WTK and win10 slipstream. In WTK we all make our own personal tweaks to setup win10 as we like it so we do not have to do those tedious tasks later on (as we do in win 7). here is my issue. I use the autounattend file in conjunction with the tweaks in WTK. I have a username (my last name) in the autounattend file to initially setup win 10 for its first boot.

I am using the win10 iso as a universal install disk for "others". I therefore have to add a new account (or user) and in win 10 I ALWAYS setup a new user with a local account as administrator. Once that is done I then can sign out of my last name account and sign into the new local account. Then I can delete my lastname account (and all its files). At this point it is now a 1 user account,  setup for the new user. However once I do that then all the tweaks are gone that I setup for my lastname account when I created this "universal" win10 iso. Win10 has the option of just changing the name of the account but if you do that the account name under USERS in file explorer does NOT change. I do not see how I can change that name. If I can change that name then problem solved. If not>>>

Is there anyway to PRESERVE the tweaks? As an example I set this pc on the desktop, show all items on taskbar, control panel on desktop to name a few.

regards...

 

Once again problem solved by doing a new install on a non VM. Its as easy or maybe even easier than win 7.

Simply go to SETTINGS then ACCOUNTS, FAMILY & OTHER USERS. Then to "add someone else to this PC."  Win 10 wants a microsoft account but if you answer you dont have the persons sign-in info then you can add a local account. Add the new user and make them an administrator. sign out then back on as the new user. Go back to that settings page and there is a choice to remove the original user. All tweaks and desktop files are not affected. BEAUTIFUL...

ps. It activated with digital license. This was a win 7 machine.

regards...

[rhahgleuhargh]

Hello,

Voici le changelog du mois :

Security Monthly Quality Rollup : KB4516065 remplace KB4512506

KB4474419 v3

KB4516655

 

 

Pas de mise à jour DNF 3.5.1. Un dernier contrôle sur les machines en installation classique et j'envoie les ULs.

Edited September 16, 2019 by rhahgleuhargh

[Thiersee]

On 9/14/2019 at 9:49 AM, rhahgleuhargh said:

....

Voici le changelog du mois :

.....

Hi,

there is another KB for september, the SSU KB4516655 (i got it requested on all my VMs)!

"Paket details" on MCU says it is a replacement for KB4490628, but it is not true, at least for installations with the "Convenience Rollup"-methode.

Putting it in WTK instead of KB4490628 (Prerequisites) gives out "Question marks" in front of some KBs, putting it in the "Updates"-section without KB4516655 in the prerequisites gives "Question marks" on other KBs, so i put it under "Updates" with KB4490628 left under "Prerequisites": no issues more!

Have a nice week.

[rhahgleuhargh]

Hello Thiersee,

Thank you for the info. Strange thing, I just checked my 4 VMs (2 classic and Convenience method for x86 and x64), and in my case this update is still not requested. Here is the result of WU in my x64 machine.

No problem, I'll update ULs.

Effectively, reading in other forums, KB4490628 is not superseeded. Once KB4516655 manually installed, Deep clean doesn't remove anything.

I'm doing a test integrating KB4516655 in prerequisites updates keeping KB4490628. Some people reported problems with september updates.

 

Edited September 15, 2019 by rhahgleuhargh

[rhahgleuhargh]

It doesn't seem to work integrating KB4516655 in prerequisite section. I'll put it in Common Updates section.

Edited September 15, 2019 by rhahgleuhargh

[abbodi1406]

SSUs are permanent updates, Deep clean do not remove them (the 3177467 v1& v2 was exception)

KB4490628 is still needed because it's SHA1-signed, and contain the infrastructure to process SHA2-signed updates

KB4474419 is also needed to recognize SHA2-only updates

 

KB4516655 is SHA2- only update, it cannot be installed without KB4490628 and KB4474419

[rhahgleuhargh]

Thanks abbodi1406 for these infos !

It works good adding KB4516655 after the 2 others.

ULs updated.

[Thiersee]

@rhahgleuhargh

KB4524157 released yesterday for Windows 7, replaces KB4516065.

KB3150220 superseeded and uninstalled (Deep Cleaning).

Tested only W7 Pro x64 on a VM (I switched to Win10 on my PC).

Regards

Edited October 4, 2019 by Thiersee

[rhahgleuhargh]

Hello Thiersee,

Yes I saw it.

I'll  wait until tuesday to update ULs, there will be more changes.

 

[mooms]

Tiens, moi aussi j'ai enfin fait le saut sur 10, et je ne le regrette pas.

J'ai profité de la réinstallation pour passer sur un SSD NVMe, et c'est clairement un cran au-dessus d'un SSD SATA, Firefox et Thunderbird s'ouvrent quasi instantanément, il y a moins d'une demie-seconde de délai entre le clic sur l'icône et le l'apparition effective de la fenêtre.

Le système en lui-même me semble plus réactif que Windows 7, mais l'OS n'étant pas le même difficile de dire si c'est le passage à 10, le NVMe, ou tout simplement l'installation fraiche.

[pennsylvaniaron]

4 hours ago, mooms said:

Tiens, moi aussi j'ai enfin fait le saut sur 10, et je ne le regrette pas.

J'ai profité de la réinstallation pour passer sur un SSD NVMe, et c'est clairement un cran au-dessus d'un SSD SATA, Firefox et Thunderbird s'ouvrent quasi instantanément, il y a moins d'une demie-seconde de délai entre le clic sur l'icône et le l'apparition effective de la fenêtre.

Le système en lui-même me semble plus réactif que Windows 7, mais l'OS n'étant pas le même difficile de dire si c'est le passage à 10, le NVMe, ou tout simplement l'installation fraiche.

Congrats mooms. I will be selling my current desktop as the holidays approach and will build a new win 10 system. I too will use a motherboard with an m.2 slot and NVMe. Can you tell me the brand and size of NVMe you are using. Is it a Samsung?

Regards...

[Thiersee]

7 hours ago, mooms said:

Le système en lui-même me semble plus réactif que Windows 7, mais l'OS n'étant pas le même difficile de dire si c'est le passage à 10, le NVMe, ou tout simplement l'installation fraiche.

I think is a bounch of all!

I switched to Win 10 since a month too, but I'll keep Win 7 until EOL because of remote-maintenance of three PCs in Italy.

My board (FM2+) does not support NVMe directly, so I used an extra-PCIe-card and a specialboot-loader (Clover).

 

Edited October 6, 2019 by Thiersee

[mooms]

Thanks pennsylvaniaron.

 

It's a Samsung 256 GB.

[pennsylvaniaron]

1 hour ago, mooms said:

Thanks pennsylvaniaron.

 

It's a Samsung 256 GB.

Nice. Samsung's prove to be the fastest. 

I've been experimenting with many clients who are upgrading to win 7. I ran into a few ACTIVATION issues, including on my VM. I've tested the following procedure and worked it every time in real world applications. I will test where I have never been able to activate. hopefully it might help some people

• Optional: Validate your copy of Windows 7 SP1 or Windows 8.x 
• Install all necessary drivers eg ethernet & wireless card
• Open your Windows 10 ISO and extract gatherosstate.exe from your desktop to your desktop
• Run gatherosstate.exe and wait for the GenuineTicket.xml file to be created
• Copy the GenuineTicket.xml to a USB thumb drive or something
• Boot to your Windows 10 USB or DVD
• Disable your internet connection
• Copy GenuineTicket.xml to \ ProgramData \ Microsoft \ Windows \ ClipSVC \ GenuineTicket \ and then reboot
• Connect online and you should be activated

Regards ...

 

Edited October 6, 2019 by pennsylvaniaron

[mooms]

I jus use Microsoft Activation Script, it simulate an upgrade from Windows 8 and make a digital activation.

Works every time.

https://pastebin.com/raw/7Xyaf15Z

 

Check your PM.

[rhahgleuhargh]

mooms Thiersee

Bienvenue sur Windows 10 !

Je ne sais pas si 10 est plus réactif que 7, mais sur ma vieille config de 2013 (I5 Sandy Bridge, vieux SSD Intel 2ème génération, 8 GO DDR3) il démarre et lance les programmes toujours au quart de tour. J'espère juste que M$ fera plus attention à soigner ses mises à jour majeures, car on a eu notre lot de bourdes avec 1809 et 1903...

7 rame de plus en plus sur mes machines virtuelles, et me fait de plus en plus penser à XP avec ses innombrables patches plus ou moins buggés. Très bon OS, mais il a fait son temps et a pris un méchant coup de vieux. De 7, je regrette quand même son orientation multimédia et sa gestion des partages réseaux qui n'est pas vraiment top avec 10, surtout avec d'autres OS...

 

 

[pennsylvaniaron]

On 10/6/2019 at 10:37 AM, mooms said:

I jus use Microsoft Activation Script, it simulate an upgrade from Windows 8 and make a digital activation.

Works every time.

https://pastebin.com/raw/7Xyaf15Z

 

Check your PM.

mooms thx will check my PM after this nice procedure for SAFE MODE in win 10. I checked this out and it works perfectly. The safe mode screen is identical to the safe mode screens in Win 7. Enjoy.

Regards...

Back in the old days with Windows 7 and 8 if your system failed you could restart your computer, while tapping the “F8” key as it was booting and it would take you to Safe Mode screens and bypass the Windows system. With Windows 10 and every time you install a new system or update it, chances you will lose the ”F8” Safe Mode Startup. Below is the procedure to reestablish this procedure. Works on all Version and Updates.


PF8 KEYS WORKING ON ALL WINDOWS 10 OPERATING SYSTEMS


Go to System CMD and open as administrator

Type Regedit

GO to and drop down through the following levels:

Hkey_Local_Machine, System, CurrentControl Set, Control, Session Manager, Configuration Manager

Under Configuration Manager, right click and create a new “Dword” called “BackupCount”.

Double click on “BackupCount” and change the value to “2”

Go back to Configuration Manager and right click on it, and create a New Key called “LastKnownGood”.

Now right click on LastKnownGood and create a “Dword” called “Enabled”.

Double click on Enabled and change the value to “1”

Exit REGEDIT and you should be back at C:\Windows\System32.

Type the following:

BCDedit /set {Current} BootMenuPolicy Legacy and hit enter.

You should see “Operation Completed Successfully”.

Exit out of Windows and restart your system.

When you see your system logo start tapping the “F8” key until the system enters the Safe Mode screen.

This screen will give you choices for startup, like Safe Mode, Safe Mode with Networking, etc.

Hope this information helps you, because it seems with Microsoft Updates or New Systems, they wipe this information from the Session Manager.

Edited October 7, 2019 by pennsylvaniaron

[Thiersee]

2 hours ago, pennsylvaniaron said:

Hkey_Local_Machine, System, Control Set, Control, Session Manager, Configuration Manager

Hi Ron,

this is a little wrong, I think it should be

Hkey_Local_Machine, System, CurrentControl Set, Control, Session Manager, Configuration Manager

One question:

do you know, if it should work with UEFI-System too?

I tried it in my UEFI-VM and it doesn't work, even if I didn't get errors;

in the BIOS- VM it works.

Regards

[pennsylvaniaron]

4 hours ago, Thiersee said:

Hi Ron,

this is a little wrong, I think it should be

Hkey_Local_Machine, System, CurrentControl Set, Control, Session Manager, Configuration Manager

One question:

do you know, if it should work with UEFI-System too?

I tried it in my UEFI-VM and it doesn't work, even if I didn't get errors;

in the BIOS- VM it works.

Regards

yes sorry about that, currentcontrol set is correct, my bad.

I would think it should work regardless because its independent of the bios since it is a change in the registry. Try it in a NON VM environment. I say that only because I had major activation issues on my VM but identical procedures worked in a non VM environment for me.

regards...

[Thiersee]

8 hours ago, pennsylvaniaron said:

I would think it should work regardless because its independent of the bios since it is a change in the registry. Try it in a NON VM environment.

Somehow it has to do with UEFI too, on my Test-PC it doesn't work too.

Only if Macrium Reflect and its boot-GUI are installed the tweak works.

But if MR and its boot-GUI are installed the Safe Mode is reachable too; OK, a bit "hidden" but reachable, so I don't need the tweak.

I installed Macrium (at least the Free Version) on all my VMs and real HW.

Please correct your post, other users will be grateful.

Regards