Does change anything if the image is assembled by MS or by someone else? I don't understand such excess of testosterone about a stupid W11 release.
The ' Definately not from microsoft ' is @ the download and its packaging . Not at whats in it . Thats why i say DOWNLOAD IT AND CHECK IT .
From the download ---- > windows-11-enterprise-ltsc-amd-64-en-us_meta.xml Code: <?xml version="1.0" encoding="UTF-8"?> <metadata> <identifier>windows-11-enterprise-ltsc-amd-64-en-us</identifier> <mediatype>software</mediatype> <collection>operatingsystemcds</collection> <creator>Microsoft, ContosoCorporation</creator> <date>2023-04-13</date> <description>It is reconstructed Windows 11 LTSC, good if you want a lightweight Windows 11 without bloatware<div>en-US and zh-CN (Coming soon) isos are include these editions:</div><div>1. Windows 11 Enterprise G</div><div>2. Windows 11 Enterprise LTSC</div><div>3. Windows 11 IoT Enterprise LTSC</div><div>All other languages isos are include these editions:</div><div>1. Windows 11 Enterprise LTSC</div><div>2. Windows 11 IoT Enterprise LTSC</div><div>Also TPM check is bypassed by using Windows 10 LTSC PE and setup engine</div><div>WARNING: If you are going to install it in BIOS mode, better just deploy install.esd or it will result in error related to Microsoft Software License Terms, I am currently figuring out how to fix that</div></description> <scanner>Internet Archive HTML5 Uploader 1.7.0</scanner> <subject>microsoft</subject> <subject>contoso</subject> <subject>contosocorporation</subject> <subject>windows11</subject> <subject>ltsc</subject> <subject>11ltsc</subject> <title>Windows 11 Enterprise LTSC</title> <uploader>@gmail.com</uploader> <publicdate>2023-04-13 19:13:16</publicdate> <addeddate>2023-04-13 19:13:16</addeddate> <curation>[curator][email protected][/curator][date]20230413191605[/date][comment]checked for malware[/comment]</curation> <year>2023</year> <collection>operatingsystemsoftware</collection> </metadata> Wich says reconstructed and <creator>Microsoft, ContosoCorporation</creator>
Might be legit just that its been reconstructed by Contoso to add EnterpriseG. I d/l another version on archive.org (Windows.11.22H2.IoT.Enterprise.LTSC) Installed on VMWare. Its in Brazilian but after going thru all transitions to make it entirely en-US this is what the version is: Edition Windows 11 IoT Enterprise LTSC Version 22H2 Installed on 6/8/2023 OS build 22621.1194 Experience Windows Feature Experience Pack 1000.22638.1000.0 All files are legit 2/01/2023
Is deployment Code: <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Deployment" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> or Code: <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Deployment" version="10.0.22621.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> or Code: <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Deployment" version="10.0.22621.1194" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> Look in Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.xxxxx.x.mum
after running WU: Edition Windows 11 IoT Enterprise LTSC Version 22H2 Installed on 6/8/2023 OS build 22621.1702 Experience Windows Feature Experience Pack 1000.22641.1000.0
Yes its strange ......... And that .xml description in english is not clear to me ......... its open to interpretation . I was wondering if someone had got a part of another microsoft product ( contoso ) that had maybe a win 11 LTSC virtual image in it and fixed it up in a 19041 basic install medium , with TPM check bypassed by using Windows 10 LTSC PE and setup engine ' IDK but i think its worth ripping apart and finding out what it is .
>check deployment versions Start . System . About ---- > EditionWindows 11 Enterprise LTSC Version22H2 Installed on08/06/2023 OS build22624.1546 ExperienceWindows Feature Experience Pack 1000.22641.1000.0
Check deployment versions in C:\Windows\servicing\Packages\Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.xxxxx.x.mum
@Ace2 ....... I cant find a file with that name ......... there is one called Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Package~31bf3856ad364e35~amd64~~10.0.22621.1470.mum It says ---- > <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Package" version="10.0.22621.1470" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <package identifier="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Package" releaseType="Feature Pack"> <update name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Deployment"> <component> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Deployment" version="10.0.22621.1470" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </component> </update> </package> </assembly>
Yep Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Package~31bf3856ad364e35~amd64~~10.0.22621.1635.mum 6/8/2023 11:00 AM
FAKE don't download. Code: Windows 11 Enterprise LTSC by Microsoft, ContosoCorporation Publication date 2023-04-13 Topics microsoft, contoso, contosocorporation, windows11, ltsc, 11ltsc It is reconstructed Windows 11 LTSC, good if you want a lightweight Windows 11 without bloatware en-US and zh-CN (Coming soon) isos are include these editions: 1. Windows 11 Enterprise G 2. Windows 11 Enterprise LTSC 3. Windows 11 IoT Enterprise LTSC All other languages isos are include these editions: 1. Windows 11 Enterprise LTSC 2. Windows 11 IoT Enterprise LTSC Also TPM check is bypassed by using Windows 10 LTSC PE and setup engine WARNING: If you are going to install it in BIOS mode, better just deploy install.esd or it will result in error related to Microsoft Software License Terms, I am currently figuring out how to fix that
Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Package" version="10.0.22621.1635" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <package identifier="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Package" releaseType="Feature Pack"> <update name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Deployment"> <component> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Deployment" version="10.0.22621.1635" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </component> </update> </package> </assembly>