Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Disable minimum system requirements?

Featured Replies

Hi again boys!

I need to disable that "minimum system requirements" check in the beginning of install.

It should be possible to change the value or disable it somewhere..

Thanks! :)


Hello again!

If you're talking about the performance test, than you can skip it by setting SkipMachineOOBE=true. This will cause a warning in WSIM, but it will skip the whole welcome procedure. AFAIK there is no other way to skip that test.

It has some disadvantages, too. It will ignore you're network location setting in Autounattend.xml for example. But you can come around this with Regtweaks.

Martin

  • Author

Actually I was aiming at the check at first boot that will stop you from installing if you don't meet the minimum requirements.

I've started to pull this thing apart and from the looks of it will 256mb of memory do just fine, so I need to remove that check that will popup and demand 512mb system memory.

:)

that is actually something built into the WinPE, not sure that it can be changed, if you wanted to ignore it you could always make a bart pe and load the WIM file on it and launch the WIM fine with Imagex

Hi Clint,

To skip that check, in Autounattend.xml, ensure that ComplianceCheck=Never.

Here it is with all the extra junk that the unattended xml code demands:

<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComplianceCheck>
<DisplayReport>Never</DisplayReport>
</ComplianceCheck>
</component>

FireGeier, that problem is solved by ensuring that NetworkLocation is configured from the oobeSystem pass.

Edited by prathapml

  • Author
Hi Clint,

To skip that check, in Autounattend.xml, ensure that ComplianceCheck=Never.

Here it is with all the extra junk that the unattended xml code demands:

<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComplianceCheck>
<DisplayReport>Never</DisplayReport>
</ComplianceCheck>
</component>

FireGeier, that problem is solved by ensuring that NetworkLocation is configured from the oobeSystem pass.

EDIT: I can't get this to work...!

Are you sure it should be a "windowsPE" title and then component name "Microsoft-Windows-Setup" ?

Thanks!

Edited by Clint

  • Author

This is killing me! :realmad:

Here is my code:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
</component>
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComplianceCheck>
<DisplayReport>Never</DisplayReport>
</ComplianceCheck>
<UserData>
<ProductKey>
<WillShowUI>OnError</WillShowUI>
</ProductKey>
</UserData>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<VerticalResolution>768</VerticalResolution>
</Display>
<UseConfigurationSet>true</UseConfigurationSet>
<DiskConfiguration>
<WillShowUI>Always</WillShowUI>
</DiskConfiguration>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OEMInformation>
<Manufacturer>The TEAM</Manufacturer>
<Model>VISTA Gamers Ed.</Model>
</OEMInformation>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Other</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<VerticalResolution>768</VerticalResolution>
</Display>
<VisualEffects>
<FontSmoothing>ClearType</FontSmoothing>
</VisualEffects>
<TimeZone>Central Standard Time</TimeZone>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:c:/vista/sources/install.wim#Windows Vista ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

I still get that darn "minimum 512mb" popup..!

Please guide me here... :whistle:

Thanks!

Edited by Clint

Tonight I am testing a few last details in the xml (image selection).

Once verified, I shall put up the entire xml as a sample working copy in this forum.

Look forward to it.

Testing my current vers Home atm & appears to unattended no probs. I found a few things so far that its far more reliable using the waik to alter the image & answer file + validate. Opposed to just editing the ans file directly with notepad etc.

Don't know for sure but with my testing found a min amount of info is required for the unattend to work flawless.

Also do not put too many unneccessary fields in there or windows will take too long to parse.

Will post my xml when fully tested.

Edited by MAVERICKS CHOICE

  • Author

Yes, a verified working basic config sample would be benefitial to a lot of newbies like me.

Thanks fellas!

:)

..the weird part is that I get my AutoUnattend passed in WAIK but it still hangs at the end of install..

..and it changes the resolution in the beginning of install so it obviously passes the entries before that...very odd.

Upon further testing, I find using Vlite to slim down the source ensures you only install the selected flavour of Vista without the annoying screen popup during ua?

More testing to be done.

Edited by MAVERICKS CHOICE

My vLite'd install source seems to refuse to install for some reason, might be something on the xml, so unfortunately it'll remain in test till the weekend. :(

EDIT: i'm noticing that posts are being formatted in weird way after submit? For example, I did not ask for a line break in above sentence.

Edited by prathapml

  • Author

Ask Nuhi where he has hidden the Unattended that is created with Vlite, or he has done a sxs package or similar...maybe in the system or components hive as well.

I seriously doubt he will answer though... :rolleyes:

Oh isn't that my bitter pal Clint taunting me again.

prathapml,

vLite doesn't use any unattended xml or anything, it does all directly.

If something for sure isn't working on vlited install and exactly the same file confirmed working on the full install then check which entries actually can't hold on...something removed. For example setting up Windows Mail with Mail removed might trigger that response. OR Images removed. Try Apply method 1. And what is the error...you may answer that with the bug report on the vLite forum.

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.