Windows 10: Announcing Windows 10 Insider Preview Build 15063 for PC and Mobile Insider

Page 11 of 109 FirstFirst ... 9101112132161 ... LastLast
  1.    21 Mar 2017 #100

    Dencal,

    no worries, I just thought it may be of interest to the forum. I've reported it thru' Feedback.

    To clarify the procedure:

    ISO made using UUP, as soon as update had downloaded. Then rebooted to ISO and clean-installed.

    dencal said: View Post
    Its not me who has a problem, I was replying to Deej post #83 requesting assistance.
    See posts #83, 86, 89, 94.
      My ComputerSystem Spec

  2. f14tomcat's Avatar
    Posts : 36,391
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       21 Mar 2017 #101

    slicendice said: View Post
    I would not count on all files existing in the Windows.old folder. There is always a small chance that some files are deleted during/after the update process. The iso may or may not work, but if for some reason there is a problem after clean installing from ISO created from the Windows.old folders, there is a high probability that at least one file is missing, which can be a disaster for Windows setup. The ISO creation could go smooth despite missing files.
    All of that is true. Just as good a chance of it being just fine and creating a perfectly usable ISO. I have done that, successfully, and used it to update. So have others. I prefer to think of it on the positive side.
      My ComputersSystem Spec

  3. slicendice's Avatar
    Posts : 3,443
    Windows 10 Pro x64 v1803 Build 17134.228 (Branch: RS4 Release Preview)
       21 Mar 2017 #102

    f14tomcat said: View Post
    All of that is true. Just as good a chance of it being just fine and creating a perfectly usable ISO. I have done that, successfully, and used it to update. So have others. I prefer to think of it on the positive side.
    I have done this successfully too, many times, but I wanted to make sure people are aware of the possibility that something could be wrong with those ISOs. Saves people from a lot of head scratches in the future. :)
      My ComputersSystem Spec

  4. M4v3r1ck's Avatar
    Posts : 632
    Win 10 Pro x64 1607 (Build 14393.953)
       21 Mar 2017 #103

    Update Sequence Start

    Click image for larger version. 

Name:	ScreenCap 2017-03-21 at 14.47.51.jpg 
Views:	19 
Size:	377.1 KB 
ID:	126034

    Cheers
      My ComputerSystem Spec

  5. Kari's Avatar
    Posts : 14,847
    Windows 10 Pro
       21 Mar 2017 #104

    f14tomcat said: View Post
    I'm probably seeing things cause I need more coffee, but looks like MS made me another 450MB Recovery partition. Swiped the space from the OS partition. Checked it with MiniTool explore option,and dates are today...this morning.

    ​Coffee..................
    f14tomcat said: View Post
    Precisely. I might add that it seems to only add a new 450MB if the new build's recovery environment is different than the current build. This is the first time it's done that here in many builds. But,it has happened before. I'm conscious of it due to the Macrium definitions getting out of kilter...shifted.

    Everybody's is a little different, that's just the way it is here.

    Something I posted a week and a half ago in another thread:

    Kari said: View Post
    By default Windows setup on clean disk creates a 450 MB recovery (RE) partition at the beginning of the disk. Logically thinking the location of this partition is wrong, which is why Windows upgrade might create a new one; upgrade needs some space to modify RE partition but can't expand it because System, MSR and Windows partitions are blocking the way, therefore upgrade creates a new one after the Windows partition shrinking it if needed thus eliminating the need to create another WinRE partition.

    An ideal disk partitioning on a GPT partitioned disk would place System (99 MB) and MSR (hidden 16 MB) partitions at the beginning of the disk, then Windows partition and add RE partition at the end of the disk:


    Unfortunately Windows setup does not follow these clear guidelines set by Microsoft, makers of Windows. Strange but true.

    To put the RE partition at end of the disk and making it somewhat bigger than default 450 MB allows upgrades to add data to it without creating a new RE partition. For an upgrade to be able to use an existing RE partition instead of creating a new one, it must have enough free space:

    • If RE partition is less than 500 MB, it must have at least 50 MB of free space
    • If RE partition is 500 MB or larger, it must have at least 320 MB of free space
    • If RE partition is larger than 1 GB, it should have at least 1 GB free

    Read more about GPT partitioning: https://msdn.microsoft.com/en-us/win...ive-partitions

    The above is why I use an answer file autounattend.xml saved on the root of the install media that then, together with another answer file unattend.xml in C:\Windows\System32\Sysprep folder automates the installation partitioning HDD as I wish, not as Windows does it if you let setup to take care of partitioning.

    An example of an autounattend.xml file, creating the EFI and MSR partitions at the beginning of the disk, Windows partition thereafter, and placing WinRE partition at the end of the disk after C: drive. When WinRE is after C: drive, it can shrink C: and expand itself if / when need arises. The product key I use in these automated installations is the generic Windows 10 PRO key.

    Partitioning in bold red font, formatting partitions correctly in bold blue font, first yellow highlight shows creating WinPE partition, second formatting it:

    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="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">
                <SetupUILanguage>
                    <UILanguage>en-GB</UILanguage>
                </SetupUILanguage>
                <InputLocale>0809:00000809</InputLocale>
                <SystemLocale>en-GB</SystemLocale>
                <UILanguage>en-GB</UILanguage>
                <UserLocale>en-GB</UserLocale>
                <UILanguageFallback>en-GB</UILanguageFallback>
            </component>
            <component name="Microsoft-Windows-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">
                <UserData>
                    <AcceptEula>true</AcceptEula>
                    <ProductKey>
                        <Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key>
                    </ProductKey>
                </UserData>
                <ImageInstall>
                    <OSImage>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>3</PartitionID>
                        </InstallTo>
                    </OSImage>
                </ImageInstall>
                <DiskConfiguration>
                    <Disk wcm:action="add">
                        <CreatePartitions>
                             <CreatePartition wcm:action="add">
                                <Order>1</Order>
                                <Size>100</Size>
                                <Type>EFI</Type>
                            </CreatePartition>
                            <CreatePartition wcm:action="add">
                                <Order>2</Order>
                                <Size>16</Size>
                                <Type>MSR</Type>
                            </CreatePartition>
                            <CreatePartition wcm:action="add">
                                <Order>3</Order>
                                <Extend>true</Extend>
                                <Type>Primary</Type>
                            </CreatePartition>
                            <CreatePartition wcm:action="add">
                                <Order>4</Order>
                                <Size>450</Size>
                                <Type>Primary</Type>
                            </CreatePartition>
                        </CreatePartitions>
                        <DiskID>0</DiskID>
                        <WillWipeDisk>true</WillWipeDisk>
                        <ModifyPartitions>
                            <ModifyPartition wcm:action="add">
                                <Order>1</Order>
                                <PartitionID>1</PartitionID>
                                <Label>System</Label>
                                <Format>FAT32</Format>
                            </ModifyPartition>
                            <ModifyPartition wcm:action="add">
                                <Order>2</Order>
                                <PartitionID>2</PartitionID>
                            </ModifyPartition>
                            <ModifyPartition wcm:action="add">
                                <Order>3</Order>
                                <PartitionID>3</PartitionID>
                                <Letter>C</Letter>
                                <Label>W10PRO-IP</Label>
                                <Format>NTFS</Format>
                            </ModifyPartition>
                            <ModifyPartition wcm:action="add">
                                <Order>4</Order>
                                <PartitionID>4</PartitionID>
                                <Format>NTFS</Format>
                                <Label>WinRE</Label>
                                <TypeID>DE94BBA4-06D1-4D40-A16A-BFD50179D6AC</TypeID>
                            </ModifyPartition>
                        </ModifyPartitions>
                    </Disk>
                </DiskConfiguration>
            </component>
        </settings>
    </unattend>

    If there's interest I could make a tutorial about this. It is one more of those things in Windows that looks complicated but is in fact really simply when you have clear instructions to do it once.

    Kari
      My ComputerSystem Spec

  6. johngalt's Avatar
    Posts : 1,534
    WinX Pro x64 IP current
       21 Mar 2017 #105

    Oddly enough, I did not see any notification for an update last night.

    Time to see if one is available now.
      My ComputersSystem Spec

  7. Brink's Avatar
    Posts : 32,415
    64-bit Windows 10 Pro build 18242
    Thread Starter
       21 Mar 2017 #106

    Update:

    No builds today, Tuesday PST #WindowsInsiders after our night flight last eve.
      My ComputersSystem Spec

  8. kado897's Avatar
    Posts : 20,901
    Windows 10 Home 64bit
       21 Mar 2017 #107

    Brink said: View Post
    Update:



    That's a relief.
      My ComputerSystem Spec

  9.    21 Mar 2017 #108

    It would be too soon, wait until tomorrow !!!! I also just updated Lumia to 55.
    PS:
    And now it's on 15063. finally a match.
    Last edited by CountMike; 21 Mar 2017 at 11:01.
      My ComputersSystem Spec

  10. martyfelker's Avatar
    Posts : 1,543
    Triple Boot Windows 10 IP Build 17711/Windows Server 2019 IP Build 17692/Debian Unsttable
       21 Mar 2017 #109

    In Windows Server 2016. Making an ISO in a Dual Boot VMware VM which I can use if Windows 10 physical can't be upgraded. Guess this is not RTM.
      My ComputersSystem Spec


 
Page 11 of 109 FirstFirst ... 9101112132161 ... LastLast

Related Threads
UPDATE: Windows 10 Insider Preview build 15058 ISO file is also now available for download here (click on link). 842858810314129408 841771427787235329 Source: Announcing Windows 10 Insider Preview Build 15058 for PC - Windows Experience...
825063872533032960 825065215523971072 825213100613775360 Source: https://blogs.windows.com/windowsexperience/2017/01/27/announcing-windows-10-insider-preview-build-15019-pc
818518109497659393 818522983345991680 Source: https://blogs.windows.com/windowsexperience/2017/01/09/announcing-windows-10-insider-preview-build-15002-pc How to Start or Stop Receiving Insider Builds in Windows 10
UPDATE: 742889757512867840 Source: Announcing Windows 10 Insider Preview Build 14366 Mobile Build 14364 | Windows Experience Blog
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 22:10.
Find Us