Page 142 of 150 FirstFirst ... 4292132140141142143144 ... LastLast
  1.    22 Aug 2017 #1411
    Join Date : Nov 2013
    Chicagoland
    Posts : 33,736
    Dual boot Windows 10 FCU Pro x 64 & Insider 10 Pro

    Quote Originally Posted by Kari View Post
    Seems to be challenging to get instructions in a way that would be understood. I am totally unable to explain it any better, my English is not enough for that.
    It's not you, Kari. It's me. Your instructions are fine. That's the path I finally used. Works fine.

    I got all the way through finally entering the correct paths. The last step:


    Click image for larger version. 

Name:	MSU Files Found.PNG 
Views:	3 
Size:	21.4 KB 
ID:	150006


    When I press enter I get this after a flash of another screen:


    Click image for larger version. 

Name:	Updates Failed.PNG 
Views:	64 
Size:	5.2 KB 
ID:	150007

    I also moved those updates to another folder I made in C:, but still failed.
    Perhaps this is because I downloaded and used the latest ISO via MCT and it has the updates added already?
      My ComputersSystem Spec
  2.    22 Aug 2017 #1412
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,951
    Windows 10 Pro

    Quote Originally Posted by HippsieGypsie View Post
    I also moved those updates to another folder I made in C:, but still failed.
    Perhaps this is because I downloaded and used the latest ISO via MCT and it has the updates added already?
    Yes, that would be the reason. Updates were rejected because your ESD made to WIM already contains them. Didn't think of adding an explanation there, should I?

    Other than that, when you finally got correct paths entered, was it too complicated to use? Did you try to write ISO files to USB, or just quit?
      My ComputerSystem Spec
  3.    22 Aug 2017 #1413
    Join Date : Nov 2013
    Chicagoland
    Posts : 33,736
    Dual boot Windows 10 FCU Pro x 64 & Insider 10 Pro

    Quote Originally Posted by Kari View Post
    Yes, that would be the reason. Updates were rejected because your ESD made to WIM already contains them. Didn't think of adding an explanation there, should I?
    Yes, if that be it. I'm learning a lot here. Your update script works great when I enter everything correctly. Here's my notes on steps I take. I realize this is not all the scenarios.



    Create folders:
    C:\ISO_Files
    C:\ TempMount
    C:\ Update_Files

    Download update files to C:\ Update_Files

    Copy ISO files to C:\ISO_Files

    Open PowerShell ISE as admin

    Check the available editions (index values) via DISM:
    dism /Get-WimInfo /WimFile:F:\Sources\install.esd

    Convert MCT ESD media to WIM via DISM:
    dism /export-image /SourceImageFile:C:\ISO_Files\Sources\install.esd /SourceIndex:1 /DestinationImageFile: C:\ISO_Files\install.wim /Compress:max /CheckIntegrity

    Delete install.esd and replace with install.wim in Sources folder

    Enter update script in PS ISE Script Editor and close

    Set Execution Policy:
    Set-ExecutionPolicy Unrestricted -Scope CurrentUser

    Press F5 to run script

    Enter: C:\ISO_Files

    Enter: ImageIndex 1

    Enter: C:\Update_Files
      My ComputersSystem Spec
  4.    22 Aug 2017 #1414
    Join Date : Nov 2013
    Chicagoland
    Posts : 33,736
    Dual boot Windows 10 FCU Pro x 64 & Insider 10 Pro

    Quote Originally Posted by Kari View Post
    Yes, that would be the reason. Updates were rejected because your ESD made to WIM already contains them. Didn't think of adding an explanation there, should I?

    Other than that, when you finally got correct paths entered, was it too complicated to use? Did you try to write ISO files to USB, or just quit?
    I just quit for now. Not complicated at all.
      My ComputersSystem Spec
  5.    22 Aug 2017 #1415
    Join Date : Jun 2014
    Posts : 5,514
    Windows 10 Pro

    Quote Originally Posted by Edwin View Post
    Today feels like a good day for a new Build!
    Sorry! MS is to busy wasting time, money and resources testing different names for the Photo app. Changing the name of apps actually makes them more productive.
      My ComputerSystem Spec
  6.    22 Aug 2017 #1416
    Join Date : Jan 2014
    Posts : 1,391
    Windows 10 Pro (32-bit) 16299.15

    Quote Originally Posted by HippsieGypsie View Post
    Perhaps this is because I downloaded and used the latest ISO via MCT and it has the updates added already?
    I'm curious about this - I did a fresh download of the MCT itself at the weekend, and used it to download an installer to a USB drive.

    But as far as I could tell, the install.esd was the same as the install.esd from an MCT I'd downloaded back in April. Same file size and I think same properties too.

    It didn't seem to download updates during that process, even though I'd hoped it would.
      My ComputerSystem Spec
  7.    22 Aug 2017 #1417
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,951
    Windows 10 Pro

    Quote Originally Posted by HippsieGypsie View Post
    Here's my notes on steps I take. I realize this is not all the scenarios.



    Create folders:
    C:\ISO_Files
    C:\ TempMount
    C:\ Update_Files
    Regarding the highlighted item in above quote, I think I need to explain something about PowerShell scripting language.

    A line starting with hash (#) is a comment, remark line that will not be executed but is included in script to explain to anyone not only using the script but also reading it what's happening, what will be done next.

    In below code box lines 43 to 45 from the script:

    Code:
    ##########################################################
    # Create a temporary working folder C:\TempMount, delete
    # old one first if folder with such name already exists
    ##########################################################

    The above lines do not mean you should create the C:\TempMount folder manually, they only explain that in next lines the folder will be created by the script. In fact, if you create the TempMount folder manually or if it exists for any reason, it will be deleted by the script and then recreated. Look at the script lines 48 to 51:

    Code:
    cls
    $Mount = 'C:\TempMount\'
    if (Test-Path $Mount) {Remove-Item $Mount}
    $Mount = New-Item -ItemType Directory -Path $Mount

    Line 48 contains the Clear Screen (cls) command which clears the PowerShell window placing cursor on top, row 1 column 1. The next line then sets value (path) C:\TempMount to variable $Mount.

    Following line, the so called IF statement checks if folder C:\TestMount exists from an earlier run, and if yes, removes it. Finally, a new item, a folder (ItemType Directory) will be created and named as C:\TempMount.

    Short: each line in script starting with # is a comment, an explanation about what the script will do next. These lines will be ignored when script is run. They are not instructions to user but instead exist to make reading and understanding the functions of the script easier for those reading it, and also for the user who wrote it, in this case me; the script contains over 400 lines, if / when I need to edit it I can find correct place faster by checking the comments before each section.

    Kari
      My ComputerSystem Spec
  8.    22 Aug 2017 #1418
    Join Date : Oct 2014
    Arnold, MD
    Posts : 28,962
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)

    Very similar concept to the Hosts file.


    # Copyright (c) 1993-2009 Microsoft Corp.
    #
    # This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
    #
    # This file contains the mappings of IP addresses to host names. Each
    # entry should be kept on an individual line. The IP address should
    # be placed in the first column followed by the corresponding host name.
    # The IP address and the host name should be separated by at least one
    # space.
    #
    # Additionally, comments (such as these) may be inserted on individual
    # lines or following the machine name denoted by a '#' symbol.
    #
    # For example:
    #
    # 102.54.94.97 rhino.acme.com # source server
    # 38.25.63.10 x.acme.com # x client host

    # localhost name resolution is handled within DNS itself.
    # 127.0.0.1 localhost
    # ::1 localhost
      My ComputersSystem Spec
  9.    22 Aug 2017 #1419
    Join Date : Nov 2013
    Chicagoland
    Posts : 33,736
    Dual boot Windows 10 FCU Pro x 64 & Insider 10 Pro

    Quote Originally Posted by Kari View Post
    Regarding the highlighted item in above quote, I think I need to explain something about PowerShell scripting language.

    A line starting with hash (#) is a comment, remark line that will not be executed but is included in script to explain to anyone not only using the script but also reading it what's happening, what will be done next.

    Kari
    Thanks for explaining, Kari. I read through the script and wondered what the hash tags were for. Now I know.

    I assume this works for any ISO files. I noticed when using the MCT it places it on the thumb drive extracted (is that the correct term?) to see all the files including the install.esd. Therefore, it's not a true ISO image, correct? It's an install drive?

    I found this on TechNet from 6 years ago: How to extract the contents from an .ISO file without burning the .ISO to disc. Office Deployment Support Team Blog

    Is there a way to extract ISO files by using Command and/or PS? I'm assuming if PS converts, it must extract as well?
      My ComputersSystem Spec
  10.    22 Aug 2017 #1420
    Join Date : Nov 2013
    Chicagoland
    Posts : 33,736
    Dual boot Windows 10 FCU Pro x 64 & Insider 10 Pro

    Quote Originally Posted by DavidY View Post
    I'm curious about this - I did a fresh download of the MCT itself at the weekend, and used it to download an installer to a USB drive.

    But as far as I could tell, the install.esd was the same as the install.esd from an MCT I'd downloaded back in April. Same file size and I think same properties too.

    It didn't seem to download updates during that process, even though I'd hoped it would.
    Good point. Unless I did something wrong, that's the result I got.

    I'm hoping some others join in here. What happened to 24c? Hmm?
      My ComputersSystem Spec

 


Similar Threads
Thread Forum
Insider Announcing Windows 10 Insider Preview Build 16237 PC for Fast ring
883370827718172672 Source: Announcing Windows 10 Insider Preview Build 16237 for PC - Windows Experience Blog How to Start or Stop Receiving Insider Builds in Windows 10
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 14946 for PC and Mobile
786612992179712000 Source: Announcing Windows 10 Insider Preview Build 14946 for PC and Mobile | Windows Experience Blog PC: How to Start or Stop Receiving Insider Builds in Windows 10
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 14942 for PC on Fast ring
784439136002375681 784446397466681344 Source: Announcing Windows 10 Insider Preview Build 14942 for PC | Windows Experience Blog How to Start or Stop Receiving Insider Builds in Windows 10
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 14388 for PC and Mobile
UPDATE: July 15th 2016 754001939445219329 752986516746493952 Source: Announcing Windows 10 Insider Preview Build 14388 for PC and Mobile | Windows Experience Blog
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 14366 & Mobile Build 14364
UPDATE: 742889757512867840 Source: Announcing Windows 10 Insider Preview Build 14366 Mobile Build 14364 | Windows Experience Blog
Windows 10 News
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 13:04.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums