Windows 11

In any event, NTLite's description needs more context because it doesn't apply to every random game.
<S2491>Fullscreen optimization for DX10/DX11 games</S2491>

DirectX Developer Blog/Updates in Graphics and Gaming
– this setting affects presentation modes used in Windowed and Borderless Windowed DX10/DX11 games.
Click to expand...
You don’t need to worry about DX12 games as they already take advantage of the new presentation mode.
Click to expand...
 
recently after making an ISO via the latest NTL build v2.3.6.8792 I've been experiencing this issue
aw0c.jpg


ISO size: 4.83 GB,
This is the first time am getting this msg while trying to install Windows 11 in my usual 120GB SSD
this partition is too small. make the size of this partition at least 179437 MB (Appx 180GB) or select another partition.
Click to expand...
Booting from USB, tried both, Rufus & ventoy (all latest versions), same result.
Never encountered this msg/issue before, on the system, using for years since Windows 10, & neither Windows minimum HDD space requirement is 180GB, that's an obnoxious & absurd size that I've never seen before in this situation.
loaded another ISO made with the previous/earlier version of NTL, no issue for that, so reporting it here.

Tagging nuhi & posting it here if anyone can help me to identify the issue.
EDIT: Stock/unedited ISO is working fine.
 
Last edited:
Shift-F10, open diskpart and disk 0 clean, convert gpt. Reboot.
Your partitioning is wrong, look at autounattend.xml. Setup displays a single partition equal to the entire boot disk.
 
Last edited:
garlin said:
Shift-F10, open diskpart and disk 0 clean, convert gpt. Reboot.
Click to expand...
Already done that, not worked, you understood the matter, it's not the error about the MBR-GPT partition mismatch
garlin said:
Your partitioning is wrong, look at autounattend.xml. Setup displays a single partition equal to the entire boot disk.
Click to expand...
I didn't do anything in the autounattend.xml, used NTL & that's created automatically via NTL while creating the ISO, & I've ben using the same settings/preset for more than 3yrs now, this is the first time getting such msg about size

I added some driver, which I usually add & added earlier as well, no issue faced earlier,
now, after receiving this msg today I exclude only 2 (heavy sizable) drivers (Intel graphics & Realtek HDA Audio) & made another ISO with the same PRESET to test, ISO size was reduced from 4.83 GB to 4.06 GB, installed without this msg pop-up

Now, making another ISO & this time excluding the Realtek HDA audio driver only, I will check it & revert here.

P.S: Earlier, in Win11 21H2 ISO, I added all the same drivers, & this msg never appeared, don't know what's wrong this time.

If you want, I can share the PRESET & the autounattend.xml
 
Setup hasn't replaced your disk layout correctly, the image shows a single partition the size of the whole disk. If we assume you're reinstalling over the same disk, there would be four previous disk 0 partitions. Since there's one, WinPE is either not recognizing the disk device or the layout cannot be followed.

All other details are immaterial to the problem. Many users, who don't use NTLite, have posted this exact error going back to W8.

What Setup is really saying (incorrectly worded) is there's no free space to add 3 other partitions. Either the disk needs unassigned space, or Setup sees 4 existing partitions of acceptable size it can re-use.

autounattend.xml should look like this example.
 

Attachments

  • autounattend.xml
    2.5 KB
this is the 'autounattend' from the latest ISO that I made, & as said earlier, this time I excluded two big driver folders
1. Realtek HDA 6.0.9239.1 (455 MB)
2. Intel Graphics 31.0.101.1999 (1.76 GB)

& ISO size reduced from 4.83 GB to 4.06 GB, & that error did not appear.

So what can be presumed from this? Faulty disk mapping inside autounattend or big driver like intel Graphics 31.0.101.1999 (1.76 GB) causing the issue?
 

Attachments

  • autounattend.xml
    3.8 KB
Big driver certainly wont help but i dont know if its the real culprit though. 99% certain i have seen others with a similar issue when integrating large drivers. keep large(extracted) drivers outside of the wim using $OEM$ and use garlin's suggestion here.

by using $OEM$ you can regularly update the driver without loading/modifying the wim file.
 
Last edited:
There's no disk layout here. Was there one before in the old preset? (looking like my example file)

Drivers aren't the issue, you're talking about modding install.wim. We're still in WinPE stage, and without a disk layout it will try to use the existing partitions. Which it can't, because it's a single one instead of 4 required for UEFI disks.

Either you restore a working disk layout by redoing Unattend's Disk template, or shift-F10 and run diskpart to reset the partition table. As always, first double check it's the right disk.
 
garlin said:
There's no disk layout here. Was there one before in the old preset? (looking like my example file)

Drivers aren't the issue, you're talking about modding install.wim. We're still in WinPE stage, and without a disk layout it will try to use the existing partitions. Which it can't, because it's a single one instead of 4 required for UEFI disks.

Either you restore a working disk layout by redoing Unattend's Disk template, or shift-F10 and run diskpart to reset the partition table. As always, first double check it's the right disk.
Click to expand...
um, IDK, I've been using the same PRESET for years, sharing the GENERIC PRESET with you
in my PRESET you can see, that I've not touched the disk layout part in the NTL post setup.

What do you suggest? Reset & reassign the NTL post setup section? I don't think the driver is the issue here, but my last test (excluding the intel driver) solved the issue so am kinda confused now & can't decide if it is about adding big sized driver or about disk mapping stage.
Clanger said:
Big driver certainly wont help but i dont know if its the real culprit though. 99% certain i have seen others with a similar issue when integrating large drivers. keep large(extracted) drivers outside of the wim using $OEM$ and use garlin's suggestion here.

by using $OEM$ you can regularly update the driver without loading/modifying the wim file.
Click to expand...
I've been using the same set of drivers for many years, it certainly increases the .WIM size & the overall ISO size of course, & occupy more in C drive while installing, but never encountered such issue ever before, so am kinda clueless here about what goes wrong in between using the same set of drivers & the same preset file. Just seen this issue with the recent W11 22H2 build recently.

As mentioned in my earlier post, I just excluded the intel graphics 31.0.101.1999 (1.76 GB) folder from the driver section, & made another ISO, & tested it, then the issue is not present.
 

Attachments

  • W11 ENT 22621.1 (June-22).xml
    26.6 KB
Last edited:
Help me understand, because this preset doesn't tell the same story.

There is no disk layout included. Which means either your ISO folder has an existing autounattend.xml which was created in a earlier pass -- or you're manually selecting the disk every time. You're integrating Intel gfx, but this preset doesn't show the <Drivers> block.

We're going to break this problem down to the simplest.

1. Take the clean 22621 image, make an ISO with no unattend. Boot and stop at the Disk screen. How many partitions does disk 0 have?
2. Take the modded image, make an ISO with no unattend. Boot again, how many partitions does disk 0 have?

The answer should be identical. And if both of them only show one partition, then the last time Setup ran something got messed up.
 
garlin said:
Help me understand, because this preset doesn't tell the same story.

There is no disk layout included. Which means either your ISO folder has an existing autounattend.xml which was created in a earlier pass -- or you're manually selecting the disk every time. You're integrating Intel gfx, but this preset doesn't show the <Drivers> block.

We're going to break this problem down to the simplest.

1. Take the clean 22621 image, make an ISO with no unattend. Boot and stop at the Disk screen. How many partitions does disk 0 have?
2. Take the modded image, make an ISO with no unattend. Boot again, how many partitions does disk 0 have?

The answer should be identical. And if both of them only show one partition, then the last time Setup ran something got messed up.
Click to expand...
I'll pm you, I think that would be a better way to discuss this, without cluttering this public thread further with anyone's individual issue.
 
Microsoft Validation OS
Microsoft Validation OS is a lightweight, fast, and customizable Windows 11-based operating system that you can use on the factory floor to diagnose, mitigate and repair hardware defects during Windows device manufacturing. Validation OS boots into a Command Line environment to increase reliability on the factory floor and supports running Win32 apps, smoothing the transition from early hardware bring-up to retail OS and apps development.
Click to expand...
Possible to run this as an ordinary OS?
 
I'd like to know how to build an updated winpe from an ms disc and use it as a desktop os.
Theres tons of PE thingys but havnt seen how to make one from an ms iso.
I'd like a slim OS for a media player/daw, dont care about gaming etc.
 
Last edited:
Clanger said:
Microsoft Validation OS

Possible to run this as an ordinary OS?
Click to expand...

Not really, it's basically a WinPE++ with additional system-level features to support build automation. While users have hacked WinPE to run real apps, it's beyond what NTLite can provide because it requires copying files from install.wim (which is not allowed by the EULA).

List #1 is which components VOS added to WinPE baseline
List #2 is which components are missing
PS C:\Users\GARLIN\downloads\PresetDiff> .\PresetDiff.ps1 bootwim.xml validation.xml
1. bootwim.xml
Windows 11 Setup (22H2) x64 - 10.0.22621.1 (en-US)

2. validation.xml
Windows 11 WinVOS (22H2) x64 - 10.0.22621.1 (en-US)

Missing Components from 1
-------------------------
accessibility_narrator 'Narrator'
bootmanagerpxe 'Boot Manager (PXE)'
cmdutils 'Miscellaneous Command Line Utilities'
complus 'COM+ (Component Services)'
componentpackagesupport 'Component Package Support'
computerbrowser 'Workstation Service (Computer Browser)'
corruptionverifier 'Corruption Verifier'
deviceupdatecenter 'Device Update Center'
diskpart
diskquota 'Disk Quota'
diskraid 'DiskRAID tool'
diskusage 'Disk Usage utility'
domainclientssvc 'IPsec Policy Agent'
efssvc 'Encrypting File System (EFS) - Service'
eventlogsvc 'Event Log'
filetrace 'File Trace MiniFilter'
grouppolicy 'Group Policy Client'
hbaapi 'Host Bus Adapter (HBA) API'
help 'Windows Help content'
helpsupport 'Help file support (CHM)'
hwsupport_floppy 'Floppy disk'
hwsupport_printer 'Printing'
hypervguest 'Hyper-V Guest'
icu 'International Unicode Components'
jscript
langarabic 'Arabic'
langbasque 'Basque'
langbulgarian 'Bulgarian'
langcatalan 'Catalan'
langchineses 'Chinese Simplified'
langchineset 'Chinese Traditional'
langcroatian 'Croatian'
langczech 'Czech'
langdanish 'Danish'
langdutch 'Dutch'
langenglishgb 'English (GB)'
langestonian 'Estonian'
langfinnish 'Finnish'
langfrench 'French'
langfrenchcanadian 'French (Canadian)'
langgalician 'Galician'
langgerman 'German'
langgreek 'Greek'
langhebrew 'Hebrew'
langhungarian 'Hungarian'
langindonesian 'Indonesian'
langitalian 'Italian'
langjapanese 'Japanese'
langkorean 'Korean'
langlatvian 'Latvian'
langlithuanian 'Lithuanian'
langnorwegian 'Norwegian'
langpolish 'Polish'
langportuguesebr 'Portuguese (Brazilian)'
langportuguesept 'Portuguese'
langpseudolocale 'Pseudo-locale'
langromanian 'Romanian'
langrussian 'Russian'
langserbian 'Serbian'
langslovak 'Slovak'
langslovenian 'Slovenian'
langspanish 'Spanish'
langswedish 'Swedish'
langthai 'Thai'
langturkish 'Turkish'
langukrainian 'Ukrainian'
langvietnamese 'Vietnamese'
manifestbackup 'Manifest Backup (WinSxS\Backup)'
mbr2gpt 'MBR to GPT conversion tool'
mdac 'Microsoft Data Access Components (MDAC)'
memorydiagnostic 'Memory Diagnostic'
microsoft.windowsnotepad 'Notepad'
msftedit 'Rich Text Edit Control (MsftEdit)'
mup 'Multiple UNC Provider (MUP)'
netbios 'NetBIOS over TCP transport'
netframeworkcommon '.NET Framework Core'
osk 'On-Screen Keyboard (Tablet PC)'
perfcounters 'Performance Counters'
rasauto 'Remote Access Auto Connection Manager'
rasmans 'Remote Access Connection Manager'
recoveryagent 'Recovery Agent'
remoteaccesssupport 'Routing and Remote Access support'
securestartup 'BitLocker Drive Encryption'
sfc 'System File Check (SFC)'
sharingcommon 'File sharing support'
smbv1 'SMB v1'
smbv2mr 'SMB v2 - Client'
smbv2server 'SMB v2 - Server'
speechapi 'Speech API'
speechcommon 'Speech Recognition'
speechtts 'Speech TTS'
storageqos 'Storage Quality of Service (Storage QoS)'
systemrestore 'System Restore'
textservices 'Text Services Framework'
timeservice 'Windows Time'
vds 'Virtual Disk Service'
vhd 'Virtual Hard Disk (VHD) support'
vss 'Volume Shadow Copy'
vssapi 'Volume Shadow Copy (API)'
vssapi32 'Volume Shadow Copy (API-32 bit)'
wininet 'Windows Internet (WinINet) - Helper and Cache'
wmitools 'Windows Management Instrumentation Tools'

Missing Components from 2
-------------------------
auditpol 'Windows Audit (Tools)'
dashost 'Device Association Service'
eventtracing 'Event Tracing for Windows (ETW)'
icm 'Image Color Management (ICM)'
kerberos32 'Kerberos Client - 32 bit'
openssh
secedit 'Local Security Policy Editor'
vwifi 'Virtual WiFi'
wcn 'Windows Connect Now (WCN)'
wfds 'Wi-Fi Direct Services Connection Manager Service'
wificloudstore 'WiFi Sync Provider'
winpeibsprovider 'WinPE IbsProvider'
winrm 'Windows Remote Management (WS-Management)'
wmicore32 'Windows Management Instrumentation - Core - 32 bit'
 
beyond our scope and probably taboo, hey ho.
i might still have my (very old, tool 1.2.0.4861)w7 barebone preset that installs at 1.26(1.16???)GB, wonder how current ntlite would deal with that ia_100000061.gif
 
A quick review of Validation OS:

Out of the box it's missing basic tools that need to be integrated from the optional CAB files. Why aren't these features built in the image?
We're talking about required features like diskpart, basic drivers, networking and PnP support.

By default, it opens a CMD shell. There is no explorer.exe.

There is no sources folder, so you can't run Setup. Both Setup.exe & sources\setup.exe abort with a winsetup.dll error 0x7E. I think someone could get it working, but it's not a simple folder copy.

Validation OS is less useful than normal WinPE for installing images. It's for OEM hardware testing, as advertised. Maybe someone will build a BartPE environment using it.
 
garlin said:
A quick review of Validation OS:
Click to expand...
one thing i noticed some time back when comparing w10 1809(think it was 1809) to its server sibling was that adding/enabling Desktop stuff in the server drastically increased resources that were used and making server no better than a client os. think i could get close to, or as good as(maybe?) a customised V-OS in resources just by disabling services.

Esoteric OS's and Editions can be more hassle than they are worth in my opinion, thats why i dont use them. even XP64 SP2 which was a good OS was a pain in the bum because of its poor hardware support.
 
Last edited:
From Google Translate:
https://www.deskmodder.de/wiki/inde...gebnisse_in_der_Suche_deaktivieren_Windows_11

Keep web search but disable search preview in search​

Microsoft has now made a change in search. Because if the web search is still activated, the news of the day and also the symbol for it are displayed in the search view. So if you want to keep the web search but don't want any news in the search, you can easily disable it. (The images have been pixelated for our security)

These settings can be found in Settings -> Privacy and Security -> Search Permissions. Depending on what you want to deactivate you will find:

1200px-Windows_11_Suche_Werbeanzeige_ausblenden_002.jpg

  • Browse cloud content
    • Microsoft Account - If it is set to "On", the username and the rewards achieved will be displayed. On "Off" these are hidden.
Windows_11_Suche_Werbeanzeige_ausblenden_003.jpg

  • More settings
    • Show Search Highlights - When set to "On" you will be shown the day's news image and associated characters in the search. If it is set to "Off", this display disappears and a local overview is displayed.
If you want to make these changes in the registry, you can find them there:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\SearchSettings
  • Microsoft Account - IsMSACloudSearchEnabled 1 = On 0 = Off
  • Work School Account - IsAADCloudSearchEnabled 1 = On 0 = Off
  • Search History - IsDeviceSearchHistoryEnabled 1 = On 0 = Off
  • Show search highlights - IsDynamicSearchBoxEnabled 1 = On 0 = Off
 
You must log in or register to reply here.
Back
Top