[MICROSOFT] Toutes les images ISO de Windows et Office (DDL)

[Joselito]

@LaDidi21,
Cela fera peut-être le bonheur des revendeurs de clés à bas prix.
Ou bien des chercheurs d'étiquettes OEM sur Le Bon Coin.

[dosibox]

En procédant ainsi, M$ encourage et stimule le marché gris de la vente de clé.

[LaDidi21]

@Joselito :
Effectivement.

__________

@dosibox :
492350f6-3a01-4f97-b9c0-c7c6ddf67d60 => Current Channel
CDNBaseUrl = http://officecdn.microsoft.com/pr/49235 ... c6ddf67d60

[dosibox]

?

+
ton lien donne : << GatewayExceptionResponse >>

[LaDidi21]

@dosibox :
C'est normal car ce n'est pas un lien mais le préfixe...

[dosibox]

C'est ce que j'ai vu après (avoir posté)
Et que voulais-tu me dire en m'envoyant cette url et "492350f6-3a01-4f97-b9c0-c7c6ddf67d60 => Current Channel
CDNBaseUrl =" ?

Sinon, quelqu'un peut m'expliquer ce qu'est : "slshim" ? => C'est un mec qui m'a parlé de ça sur un forum en mp. Je lui ai demandé ce qu'est ce terme mais je n'obtiens pas de réponse de sa part
Même en googlant, je ne comprends pas bien.

[LaDidi21]

@dosibox :
le GUID 492350f6-3a01-4f97-b9c0-c7c6ddf67d60 dans l'URL indique que c''est du CC (Current Chnanel).

Sorti de son contexte, "slshim" ne veut rien dire. A part si SL est une abréviation => "System Licensing Shim" ?

Pas compris ta question sur le shim car c'est toi qui a parlé de ohook ?
cf. Windows 10 Trial Watermark
Si tu ne connais pas le langage C n'as jamais de développement système, je doute que tu psuisses comprendre...

Code : Tout sélectionner

How to use slshim
-----------------
Replace slc.dll, sppc.dll, slcext.dll, sppcext.dll and slwga.dll with
appropiate 32/64 bit version of SLShim. After a reboot, windows is
completely cut off from sppsvc - which may scream about it internally,
so you may as well disable it.

Some software, such as Office carries its own copy of sppsvc called
'osppsvc' .. usually found at

%CommonProgramFiles%\Microsoft shared\OfficeSoftwareProtectionPlatform

just replace dll in there with slshim if you don't want to install it
system-wide.

SLShim also runs as a background service to keep kernel policy
cache in sync with our overrides. This service is non-vital if you
don't plan to further tinker with those values, ie after first reboot
when the crtical values are synced, you can manually disable it.

All of the above is configured automatically by the 'install.bat' script, but
the architecture is modular. In particular:

* You can run only the slshim service. It will configure kernel policies, and
  nothing else.

* You can replace only office dll.

* It is not recommended to replace just "some" of the 5 files under
  Windows\system32. While SLShim is designed to not crash stuff under such
  circumstance, it will generally not function as intended (the non-replaced
  apis will simply claim the SL service is not available at all).

How to configure SLShim[code]

-----------------------
[HKEY_LOCAL_MACHINE\SYSTEM\Tokens]
----------------------------------

This is the general token configuration used to answer SLGetApplicationPolicy
queries, so called feature killbits. Some tools, such as rdpwrap spoof these
value in process - we do it globally.

Typically, the values are answered 1:1 to template in the registry, but there
are some fields with special meaning:

1) APPids and SKUs
------------------

Generally, SLShim tries to come up with some garbage and throw it at the
API user. This does not always work (office). In that case we need to
precisely list APPID associated SKUID explicitly:

{APPID} = REG_MULTI_SZ {skuid}, {skuid}....

Usually, you need only one SKU per APPID, but occasionaly you may need to
add another (it is a REG_MULTI_SZ) to enable certain feature identified by
that SKU.

2) Wildcards and deadbeef
-------------------------

To avoid enumerating every possible policy setting, we can set a wildcard,
for example:

"office-*"=dword:00000001

Will answer anything matching this pattern with said DWORD. Most of policies
are simple boolean flags "is this feature enabled?" naturally, we answer
yes to everything. This is not always desirable though, Sometimes we want
to answer that the value simply does not exist:

"office-IsPhoneOnly"=dword:deadbeef

(answering 1 would conflict with other settings and the software won't start).

Naturally, exact matches take precedence over wildcard. More generally,
longest match has the highest precedence (in case you set up multiple
layers of wildcard).

Back to dword:deadbeef, it is a special marker - it forces the API to
answer 'nope, this policy does not exist', regardless of wildcard.

This is because we don't actually know the correct value expected,
and API trace shows that indeed, the value does not exist in common
SKU certificates.

Both wildcards and deadbeef is important to discover proper policies
expected by the API user.

3) Populate=DWORD:1
This keyword is not a policy, but a flag used by SLShim itself to 
enable API tracing.

If it's set to non-0, whenever a wildcard is matched, all the policy
names asked and values we answered (ie the value from wildcard) will be
written into registry:

"office-30CAC893-3CA4-494C-A5E9-A99141352216"=dword:00000001
"office-AppPrivilege.ProEE-DRM"=dword:00000001
"office-AppPrivilege.ProXML"=dword:00000001
"office-AppPrivilege.VisioDataFeature"=dword:00000001
"office-AppPrivilege.ProEE-Classify"=dword:00000001
.... ton of others

This is useful so you can easily find out which policy is "poison".
Now you can keep assigning 'deadbeef' to those entries, one by one or in
bunch until stuff starts working. Finally you pin point exact 'poison' entries.

It is not recommended to remove the wildcard, as new entries will start
appearing while you're doing this (it's called bisecting). Software asks
for different policies depending on currently presented policies.

Eventually, this is how I found about the dozen of values which can't be
simply DWORD 1 for office 2016:

for example:
"office-PreviewExpireDate"=dword:deadbeef
"office-TrialType"=dword:deadbeef
"office-DemoMode"=dword:deadbeef
"office-DisallowPhone"=dword:deadbeef

Many are self-explanatory. For something entirely new you have no idea
about, you may need to set pure wildcard, for example '*'=dword:deadbeef
(ie log asked entries, but claim those dont exist). And gradually twak it.

And beware, software using ClickToRun uses split-view registry. That is,
all writes are redirected to private registry space, for example:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\SYSTEM\Tokens

This is where the results of 'Populate' may appear, instead of being dumped
into HKLM\SYSTEM\Tokens.

ClickToRun first tries to read value from this space, and if it does not
succeed, it tries the original HKLM\System\...

[HKEY_LOCAL_MACHINE\SYSTEM\Tokens\Kernel]
-----------------------------------------

This key contains "core windows" policy overrides - things which make windows
different between editions. Partial documentation of values found in there can
be found at:

http://www.geoffchappell.com/notes/windows/license/install.htm
http://forums.mydigitallife.info/threads/39411-Windows-Product-Policy-Editor

Changes apply in real time for most value queries made via
SLGetWindowsInformation - which most of windows does, but not all -

Some windows components ask the kernel cache directly about policy settings
they bypass the usual SPPSVC API we hook into. As well as kernel itself consults
its cache for values it needs - such as Kernel-WindowsMaxMemAllowedx86 (PAE).

Such fields are generally prefixed 'kernel-*', but this is not consistent. For
example 'WSLicensingService-EnableLOBApps' (enable metro sideloading) is
through obfuscated kernel API, again, directly bypassing SPPSVC API of ours.

Hilariously, notepad does this too, through inconspicuous call
to WinSqmIncrementDWORD which totally is not just:

SLGetWindowsInformationDWORD('Security-SPP-GenuineLocalStatus')

Good one, Bill.

With win8 onwards, these calls are heavily obfuscated and difficult to emulate
(search MDL for codename 'WARBIRD'). This is why we simply convince kernel
of values of our choice, so everything works as "usual".

We do this by reflecting our overrides back into the persistent kernel cache
which gets loaded on boot (ProductOptions). Contrary to popular belief, it's
not necessary to boot into WinPE to do that, just edit stuff and simple reboot
suffices.

How the cache works exactly:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions
ProductPolicy=BINARY .... big blob

This big blob is just encoded tokens you see under SYSTEM\Tokens\Kernel.
Whenever you change value under \Kernel, it will be updated back into
ProductOptions.

Underscores
-----------
You'll see most of entries in \Kernel ending with underscore - '_'. These
entries are purely informational, are never used, and dumped into the registry
so that we know what policies the kernel cache currently knows about. Once you
find some field in there you want to override, simply remove the underscore
and the value becomes active.

This is a bit similiar to the Populate DWORD, but different in that the dumped
values never interfere with the policies in kernel by default. It would be
dangerous to have those values 'frozen', as certain windows subsystems expect
these entries to be variable, especially kernel components of sppsvc/clipsvc.

[LaDidi21]

@marc4night :
Commence par relire ta "présentation"

[Joselito]

@LaDidi21 & all,
Pour les machines virtuelles cela semble s'arranger.
https://github.com/massgravel/Microsoft ... on-Scripts

[dosibox]

@LaDidi21 : merci pour ton post mais tes deux liens : [url)https://blogs.technet.microsoft.com/ask ... new-stuff/]Shim[/url] + ohook ne fonctionne pas car ils renvoient vers https://techcommunity.microsoft.com/t5/ ... -p/AskPerf

@Joselito : de quelle façon ça s'arrange ?

[LaDidi21]

@dosibox :
Liens pourris... corrigés.

[dosibox]

@LaDidi21 : https://blogs.technet.microsoft.com/ask ... new-stuff/ me renvoie toujours vers https://techcommunity.microsoft.com/t5/ ... -p/AskPerf
Donc je ne peux pas lire la page en anglais

[LaDidi21]

@dosibox :
Décidément seulement 50 % de corrigé
Demystifying shim - or - Using the App Compat Toolkit to make your old stuff work with your new stuff

[dosibox]

Merci à toi.

[Bill_Boquet]

@LaDidi21 & all,
Pour les machines virtuelles cela semble s'arranger.
https://github.com/massgravel/Microsoft ... on-Scripts

Merci pour les niouzes @Joselito. Pour les curieux, la nouvelle méthode d'activation HWID est expliquée dans le dernier lien ci-dessous :
https://github.com/massgravel/Microsoft ... s/releases
v2.2 A New Hope For HWID Latest
Changelog: 2.2
HWID:
A new method is discovered to activate with HWID. https://massgrave.dev/hwid.html Thanks a lot to the @asdcorp and team for the discovery.

[dosibox]

Merci Bill_Boquet, c'est bien expliqué
Très bonne nouvelle qu'ils ont trouvé une faille/un exploit appelé maintenant HWID 2.
https://forums.mydigitallife.net/thread ... st-1808641

HWID 2 (Currently working) (03 Oct 2023 - Current)
When Microsoft stopped the free upgrade, it started requiring Genuine valid key in ticket to authorize a digital license. In the new method we used only the Installation ID of a genuine, valid key. This gets accepted by the server and allows us to get a digital license for free. Check manual activation process in below section to know how to make working universal tickets.
Now a question, can Microsoft block the new requests or revoke already established HWID license?

Revoking the license would be too extreme and will face many complications and risk of voiding valid licenses. However they can block the new activation requests for new hardware coming from the methods mentioned here.

Mais HWID 2 est seulement compatible avec les machines virtuelles ?

[Joselito]

@dosibox,
Mais non !

[dosibox]

Ok, merci Joselito.

https://uupdump.net n'est plus actif comme site Internet ?

[balou le fou]

@Dosibox, ils sont en .cn maintenant de mémoire

[Fazer]

Ok, merci Joselito.

https://uupdump.net n'est plus actif comme site Internet ?

Code : Tout sélectionner

TWL2.32766D22766D376E616C6F3F25656E2075757E2777777F2F2A3370747478 6

[dosibox]

@Fazer : Merci PaTron.

@balou le fou : https://uupdump.cn donne pour résultat :

Error 400 -- 域名未绑定 （请勿频繁刷新本页面,否者您的宽带IP将会被屏蔽）
Error 400 -- Event ID: web server ovh-2
错误URL：https://uupdump.cn/
错误msg：host not found.
节点ID：web server ovh-2
(请勿频繁刷新本页面,否者您的宽带IP将会被屏蔽)
如果您是网站管理员，查看下方原因解决。

可能原因:
① 主机没有绑定这个访问的域名地址，请在控制面板中绑定相应的访问地址
节点ID: web server ovh-2
违法和不良信息举报|知识产权侵权举报|欺诈、钓鱼举报|恶意行为举报
联系我们
投诉邮箱: cdncomplaint@gmail.com

[balou le fou]

@Dosibox, Ah mayrde.

Désolé, c'est sur ce lien là que j'avais été la mois dernier. Heureusement @Fazer nous sauve tous

EDIT: Mon lien enregistré dans mes favoris fonctionnent toujours en .cn

Code : Tout sélectionner

TWL2.33757D2E656D376E616C6F3F2E636E207D65746075757E2777777F2F2A33 707474786

[dosibox]

Ah oui en effet, ton lien avec les www fonctionne. Merci.

[dosibox]

Je viens d'installer Windows 11 ( depuis fr-fr_windows_11_consumer_editions_version_22h2_updated_sep_2023_x64_dvd_9c03e083.iso ) sur un ordinateur et désinstaller direct onedrive. Microsoft ne sait pas faire de désinstallation propre concernant ce programme : il reste 50 Mo de données sur le disque après désinstallation

3 dossiers :
C:\Users\XXXX\OneDrive
C:\Users\XXXX\AppData\Local\OneDrive
C:\Users\XXXX\AppData\Local\Microsoft\OneDrive

Je ne parle même pas des clés de registre où je n'ai pas cherché mais il doit sûrement en rester après désinstallation d'onedrive.

[Bill_Boquet]

@All : Pour info, le site de MAS offre maintenant en téléchargement les toutes dernières versions des ISO officielles Windows et Office.
https://massgrave.dev/genuine-installation-media.html
Tout y est (sauf Windows 98 ), y compris des explications claires (e.g. genuine verfication).
A voir si les mises à jour mensuelles seront proposées rapidement dans le futur, auquel cas c'est la panacée.
Enjoy

[dosibox]

Merci de l'information PaTron.

[SOUFIEN]

Salut tout le monde
Office Professionnel Plus 2021 x64 & x86 a été mis à jour par Microsoft
Version 2309 (Build 16.0.16827.20130).
Si quelqu'un peut nous donner le lien direct pour le télécharger depuis le site officiel.
Merci

[LaDidi21]

@SOUFIEN ;
Pour quelqu'un qui

... maîtrise tous les outils de microsoft office ...

tu m'inquiètes.
ODT, tu ne connais pas ?