New Windows 10 Insider Preview Slow Build 17713.1002 - July 26 Insider

Page 18 of 44 FirstFirst ... 8161718192028 ... LastLast

  1. Posts : 50,055
    Windows 10 Home 64bit 21H1 and insider builds
       #170

    cereberus said:
    There is a bug in the installer that hides the skip pin option that affects some users.

    The easiest way round it is to setup a local account during installation, and change to MS account later.
    Thanks. I did wonder.
      My Computer


  2. Posts : 1,937
    win 10 Insider
       #171

    Been noticing my comp waking from sleep with this version. The hard disk light ticks away but Task Manager doesn't seem to show disk activity. There is low level CPU activity and often it seems it is the Windows Shell Experience Host causing it.

    This comp has been a good reliable sleeper so it seems this build is at fault.
      My Computers


  3. Posts : 15,485
    Windows10
       #172

    kado897 said:
    Thanks. I did wonder.
    The irony here is Fast Ring users cannot officially test a clean install sequence as we only ever officially get upgraded, and the Insider Programme does not recognise our self made isos.

    Worse still, MS have not even released a Slow Ring iso which is rather baffling as that seems to be a policy shift - in the past an iso always followed a Slow Ring release within a week or so.

    So how does MS expect us to (officially) test the installer if the iso is only released when RTM?
      My Computer


  4. Posts : 50,055
    Windows 10 Home 64bit 21H1 and insider builds
       #173

    cereberus said:
    The irony here is Fast Ring users cannot officially test a clean install sequence as we only ever officially get upgraded, and the Insider Programme does not recognise our self made isos.

    Worse still, MS have not even released a Slow Ring iso which is rather baffling as that seems to be a policy shift - in the past an iso always followed a Slow Ring release within a week or so.

    So how does MS expect us to (officially) test the installer if the iso is only released when RTM?
    Exactly.
      My Computer


  5. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #174

    cereberus said:
    The irony here is Fast Ring users cannot officially test a clean install sequence as we only ever officially get upgraded, and the Insider Programme does not recognise our self made isos.

    Worse still, MS have not even released a Slow Ring iso which is rather baffling as that seems to be a policy shift - in the past an iso always followed a Slow Ring release within a week or so.

    So how does MS expect us to (officially) test the installer if the iso is only released when RTM?
    kado897 said:
    Exactly.
    Because it's a waste of time at early stages of new feature development. They focus on the bare minimum configurations for the setup/upgrade part and the rest is only adding new features and fixing bugs on the main system image. If they'd rebuild and re-configure every single build for all environment changes they make, it would not be that cost effective and we would not be this far with Windows 10 as we are right now.
      My Computers


  6. Posts : 2,205
    WINDOWS 10 Pro x64 build 19042.685
       #175

    In another comment I had talked about "Windows Timeline Support", it is now officially available: Chrome web store.
    New Windows 10 Insider Preview Slow Build 17713.1002 - July 26-timeline-chrome.jpg
      My Computer


  7. Posts : 15,485
    Windows10
       #176

    slicendice said:
    Because it's a waste of time at early stages of new feature development. They focus on the bare minimum configurations for the setup/upgrade part and the rest is only adding new features and fixing bugs on the main system image. If they'd rebuild and re-configure every single build for all environment changes they make, it would not be that cost effective and we would not be this far with Windows 10 as we are right now.
    But we are not at an early stage! MS have signaled they are not going to develop it significantly now until release. Insiders should test all phases including clean install now. The pin bug I mentioned is a good example - we should be able to detect such bugs asap so MS can remedy.

    I am not saying all releases should have an iso, but we are long overdue a slow ring iso.
      My Computer


  8. Posts : 17,661
    Windows 10 Pro
       #177

    badrobot said:
    It's been a long while since I did a clean install. Big change. So many questions during installation. Quite annoying but can't complain. :)Attachment 195806
    kado897 said:
    I couldn't find a way of not creating a pin. Most annoying.
    kado897 said:
    Yes I kept saying no thanks and it always came back as would you like to create a pin. Couldn't see a skip option so I took the easy way out and created one. No biggie.
    @badrobot @kado897 & Co.:

    Sysprep comes to rescue! Doing the following adds two three minutes to your clean install time but is worth of it, you gain it back by completely bypassing OOBE with all "Choose this, click that".

    Quick Start instructions to A) completely bypass OOBE asking this and that, and B) always keep an upgraded "clean install" media in case you need to clean install for any reason.

    1.) Copy the below code to a new Notepad text file, save it as unattend.xml (remember to select Save as type: All files in Notepad Save dialog!):

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>0809:00000809</InputLocale>
                <SystemLocale>EN-GB</SystemLocale>
                <UILanguage>EN-GB</UILanguage>
                <UILanguageFallback>EN-GB</UILanguageFallback>
                <UserLocale>EN-GB</UserLocale>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OOBE>
                    <VMModeOptimizations>
                        <SkipAdministratorProfileRemoval>false</SkipAdministratorProfileRemoval>
                    </VMModeOptimizations>
                    <HideEULAPage>true</HideEULAPage>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <ProtectYourPC>1</ProtectYourPC>
                    <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
                </OOBE>
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Description>Local admin account</Description>
                            <DisplayName>Your Name</DisplayName>
                            <Group>Administrators</Group>
                            <Name>Your Name</Name>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
                <RegisteredOrganization>Any org name, real or fictional</RegisteredOrganization>
                <RegisteredOwner>Your name</RegisteredOwner>
            </component>
        </settings>
    </unattend>
    Change following before saving:
    • processorArchitecture="amd64" is for 64 bit Windows, change adm64 to x86 in 32 bit Windows. This setting appears twice in the code.
    • InputLocale and other region and keyboard settings, change as follows:
      • Brazil - Portuguese > 0416:00000416, pt-BR
      • Canada - English > 1009:00000409, en-CA
      • Canada - French > 0c0c:00011009, fr-CA
      • France - French > 040c:0000040c, fr-FR
      • Germany - German > 0407:00000407, de-DE
      • UK - English > 0809:00000809, en-GB
      • USA - English > 0409:00000409, en-US
      • For other locales, see complete list: Default Input Profiles (Input Locales) in Windows | Microsoft Docs
    • Your name, appears three times. Change to username you want to use for your account
    • RegisteredOrganization, change to any real or fictional org name you want to use

    2.) Copy the unattend.xml file to your Windows 10 install media.

    3.) Disconnect computer from Internet (remove Ethernet cable). Clean install Windows normally until OOBE starts and you are shown the region and keyboard selection screen. Do not select region, instead press SHIFT + F10 to open Command Prompt. Close it as soon as it has opened, we only needed open it once to activate WIN-key shortcuts.

    4.) Press WIN + E to open File Explorer, copy unattend.xml from install media to C:\Windows\System32\Sysprep folder:

    New Windows 10 Insider Preview Slow Build 17713.1002 - July 26-image.png

    5.) Click OK to run Sysprep with default settings:

    New Windows 10 Insider Preview Slow Build 17713.1002 - July 26-image.png

    6.) Windows will restart and run a completely automated OOBE. It stops first on sign in screen, where you can set the account password. If you prefer not to use a password, simply click the Submit button:

    New Windows 10 Insider Preview Slow Build 17713.1002 - July 26-image.png

    New Windows 10 Insider Preview Slow Build 17713.1002 - July 26-image.png

    7.) When on desktop, connect to Internet and install Macrium Reflect. Install the basic software you want to be included in image, customize Start and Desktop. Create full system image with Reflect.

    8.) When new feature upgrade will be released, create an ISO of it.

    9.) Open the Macrium system image in Macrium viBoot (tutorial), selecting network: Not connected

    10.) Upgrade viBoot VM from ISO

    11.) Save viBoot image as new full image.

    That's it. Next time you need to clean install, simply restore the latest viBoot image.

    Kari
      My Computer


  9. Posts : 50,055
    Windows 10 Home 64bit 21H1 and insider builds
       #178

    Kari said:
    @badrobot @kado897 & Co.:

    Sysprep comes to rescue! Doing the following adds two three minutes to your clean install time but is worth of it, you gain it back by completely bypassing OOBE with all "Choose this, click that".

    Quick Start instructions to A) completely bypass OOBE asking this and that, and B) always keep an upgraded "clean install" media in case you need to clean install for any reason.

    1.) Copy the below code to a new Notepad text file, save it as unattend.xml (remember to select Save as type: All files in Notepad Save dialog!):

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>0809:00000809</InputLocale>
                <SystemLocale>EN-GB</SystemLocale>
                <UILanguage>EN-GB</UILanguage>
                <UILanguageFallback>EN-GB</UILanguageFallback>
                <UserLocale>EN-GB</UserLocale>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OOBE>
                    <VMModeOptimizations>
                        <SkipAdministratorProfileRemoval>false</SkipAdministratorProfileRemoval>
                    </VMModeOptimizations>
                    <HideEULAPage>true</HideEULAPage>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <ProtectYourPC>1</ProtectYourPC>
                    <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
                </OOBE>
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Description>Local admin account</Description>
                            <DisplayName>Your Name</DisplayName>
                            <Group>Administrators</Group>
                            <Name>Your Name</Name>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
                <RegisteredOrganization>Any org name, real or fictional</RegisteredOrganization>
                <RegisteredOwner>Your name</RegisteredOwner>
            </component>
        </settings>
    </unattend>
    Change following before saving:
    • processorArchitecture="amd64" is for 64 bit Windows, change adm64 to x86 in 32 bit Windows. This setting appears twice in the code.
    • InputLocale and other region and keyboard settings, change as follows:
      • Brazil - Portuguese > 0416:00000416, pt-BR
      • Canada - English > 1009:00000409, en-CA
      • Canada - French > 0c0c:00011009, fr-CA
      • France - French > 040c:0000040c, fr-FR
      • Germany - German > 0407:00000407, de-DE
      • UK - English > 0809:00000809, en-GB
      • USA - English > 0409:00000409, en-US
      • For other locales, see complete list: Default Input Profiles (Input Locales) in Windows | Microsoft Docs

    • Your name, appears three times. Change to username you want to use for your account
    • RegisteredOrganization, change to any real or fictional org name you want to use

    2.) Copy the unattend.xml file to your Windows 10 install media.

    3.) Disconnect computer from Internet (remove Ethernet cable). Clean install Windows normally until OOBE starts and you are shown the region and keyboard selection screen. Do not select region, instead press SHIFT + F10 to open Command Prompt. Close it as soon as it has opened, we only needed open it once to activate WIN-key shortcuts.

    4.) Press WIN + E to open File Explorer, copy unattend.xml from install media to C:\Windows\System32\Sysprep folder:

    New Windows 10 Insider Preview Slow Build 17713.1002 - July 26-image.png

    5.) Click OK to run Sysprep with default settings:

    New Windows 10 Insider Preview Slow Build 17713.1002 - July 26-image.png

    6.) Windows will restart and run a completely automated OOBE. It stops first on sign in screen, where you can set the account password. If you prefer not to use a password, simply click the Submit button:

    New Windows 10 Insider Preview Slow Build 17713.1002 - July 26-image.png

    New Windows 10 Insider Preview Slow Build 17713.1002 - July 26-image.png

    7.) When on desktop, connect to Internet and install Macrium Reflect. Install the basic software you want to be included in image, customize Start and Desktop. Create full system image with Reflect.

    8.) When new feature upgrade will be released, create an ISO of it.

    9.) Open the Macrium system image in Macrium viBoot (tutorial), selecting network: Not connected

    10.) Upgrade viBoot VM from ISO

    11.) Save viBoot image as new full image.

    That's it. Next time you need to clean install, simply restore the latest viBoot image.

    Kari
    Thanks Kari. I think I'll pass on that.
      My Computer


  10. Posts : 17,661
    Windows 10 Pro
       #179

    kado897 said:
    Thanks Kari. I think I'll pass on that.
    Of course that is your choice. I just want to say that although the instructions might look complex, it is in fact an extremely easy procedure and as I mentioned, does only take a few minutes.

    Kari
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:47.
Find Us




Windows 10 Forums