Create Windows 10 ISO image from Existing Installation  

Page 28 of 50 FirstFirst ... 18262728293038 ... LastLast

  1. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #270

    slicendice said:
    Go to https://insider.windows.com and join the insider program. Then go download the latest ISO they have released. Install it in a VM or any spare physical computer using either the ISO file or by creating a bootable thumbdrive explained in the tutorial Create Bootable USB Flash Drive to Install Windows 10 or simply burning the ISO to a DVD and then installing on a physical computer.

    Then go to UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files tutorial and follow the instructions to the letter.
    I've written a tutorial about this, how to use Hyper-V VM to get latest Windows Insider Fast Ring build ISO: Use Hyper-V virtual machine to get Windows 10 Insider ISO Windows 10 Virtualization Tutorials
      My Computer


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

    Kari said:
    I've written a tutorial about this, how to use Hyper-V VM to get latest Windows Insider Fast Ring build ISO: Use Hyper-V virtual machine to get Windows 10 Insider ISO Windows 10 Virtualization Tutorials
    Forgot about that one. Thanks for adding this. Great tutorial with all needed links in one place.:)
      My Computers


  3. Posts : 4
    Windows 10 Enterprise LTSB 2016
       #272

    slicendice said:
    1. desktop.ini files are hidden and protected operating system files you should not worry about. They are used to make sure that a folder has correct icon and icon-resolution, among other things.
    slicendice said:

    2. Those hidden files and folders you are referring to are mostly Operating System files, and you should not tamper with them. Then there are also hidden folders which you should not touch. They are all needed by the system. The Users folder should ALWAYS have the Default and Public user folders. I suggest you follow the tutorial to the letter.

    yes, I followed the tutorial to the letter​, I promise.

    BUT... I didn't ask if I could delete those files/folders after I boot to desktop as a new User, I know they are important files for the system, I was asking:

    why do I have it?

    When I install a clean Windows (without running audit/sysprep/etc), and I click on "Show hidden files and folders", I don't have these files and folders. I see the hidden ProgramData, but not the other folders (i.e.: $Recycle.Bin, Documents and Settings, Programs, Recovery, System Volume Information) and files (bootmgr and BOOTNXT) in C:. And, I don't see a desktop.ini in every single folder. And, in Computer>C:>Users I usually see Default and Public folders, but I don't usually see All Users, Default User, defaultuser0, defaultuser0.DESKTOP-*code*, and defaultuser-DESKTOP-*another code*.

    Why do I have these things? Is there a way to hide them? I don't want to delete them, just don't see them. In a clean installation of Win I don't have them (or I don't see them, very different), so I was wondering if I could avoid to see them now too.

    Maybe is this something related to admin account?

    Thanks again for your patience :)
    Last edited by Judoludo; 03 Aug 2017 at 12:51. Reason: forgot quote
      My Computer


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

    Judoludo said:
    yes, I followed the tutorial to the letter​, I promise.

    BUT... I didn't ask if I could delete those files/folders after I boot to desktop as a new User, I know they are important files for the system, I was asking:

    why do I have it?

    When I install a clean Windows (without running audit/sysprep/etc), and I click on "Show hidden files and folders", I don't have these files and folders. I see the hidden ProgramData, but not the other folders (i.e.: $Recycle.Bin, Documents and Settings, Programs, Recovery, System Volume Information) and files (bootmgr and BOOTNXT) in C:. And, I don't see a desktop.ini in every single folder. And, in Computer>C:>Users I usually see Default and Public folders, but I don't usually see All Users, Default User, defaultuser0, defaultuser0.DESKTOP-*code*, and defaultuser-DESKTOP-*another code*.

    Why do I have these things? Is there a way to hide them? I don't want to delete them, just don't see them. In a clean installation of Win I don't have them (or I don't see them, very different), so I was wondering if I could avoid to see them now too.

    Maybe is this something related to admin account?

    Thanks again for your patience :)
    Those are protected operating system files, they are there but the default is to hide them when entering the normal desktop mode. If you wanna check all files and folders, even the protected ones, then fire up Explorer and go to View-->Options-->Change folder and search options, then go to the view tab and there untick the "Hide protected operating system files".

    Now you can see all files on your system.
      My Computers


  5. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #274

    Judoludo said:
    BUT... I didn't ask if I could delete those files/folders after I boot to desktop as a new User, I know they are important files for the system, I was asking:

    [B][I][U]why do I have it?
    You have those files and folders because every single Windows installation has them, regardless if installed from official Microsoft install media or self made customized ISO. Windows needs them. By default they are protected and hidden, never shown if the user (you!) has not specifically chosen to show them.

    By default, this is the content of C: drive in 64 bit Windows 10 after installation:

    Create Windows 10 ISO image from Existing Installation-image.png

    The same when user has selected to show hidden files:

    Create Windows 10 ISO image from Existing Installation-image.png

    And the same when user has also selected to show protected system files and folders:

    Create Windows 10 ISO image from Existing Installation-image.png

    Those files and folders are shown on your system because you yourself have selected to show them.

    Kari
      My Computer


  6. Posts : 4
    Windows 10 Enterprise LTSB 2016
       #275

    oh perfect, so it was the untick on "Hide System Protected Files".

    Thank you :)
      My Computer


  7. Posts : 307
    Windows 10
       #276

    A curious question: In the part four, when the Windows 10 DVD is started and then you press the Shift+F10 sequence to open the Command Prompt, is Windows PE or Windows RE started?

    Thanks

    Bye
      My Computer


  8. Posts : 4
    Windows 10 (1703 build 1506)
       #277

    custom.ISO with 'remote desktop' issue


    Hi Kari and others,

    I used the PartII/IV/V procedure and created an 'almost' correctly functioning custom ISO, but there is a hangup that appears when I test the ISO in Hyper-V. I don't know if this is an ISO creation issue, or a "ISO running in Hyper-V" issue. Neither symptom described below is observed with the official WinISO. I've exhausted my brain and the web... so I'm turning to posting for help :)

    My questions are:
    #1 Should my custom.ISO install *and* auto-restart in the Hyper-V VM?
    #2 Have I made a correctly functioning ISO image of my system?
    #3 Can the custom.ISO be fully validated in a VM, or do I need o install to an SSD?
    #4 Perhaps I need to disable some options/components before making install.wim?

    Symptom #1:
    1) Creating the custom install.wim, building the custom ISO, and installing the custom ISO in Hyper-V is successful up to the point where the Win10 installation restart counter hits zero, upon which the counter disappears resulting in a plain blue background. The system does not restart in the VM like the official Win1703 ISO install does.
    --I turn off and restart the VM (since guest OS shutdown gives an error), and Win10 proceeds quickly through boot>UserLogin>desktop perfectly fine. I previously had issues with restart request notices for a specific program (HotKey) appearing 1.5 minutes after login, but disabling that application in TaskManager>Startup before making custom.wim solves the problem.

    Symptom #2:
    1) Restarting the guest OS for the second time using the Win10 start menu proceeds fine, until immediately after login when a light blue screen appears with the message: "The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Other users should still be able to log on." **If not acknowledged with by clicking okay, the system eventually loads.
    2) Restarting guest OS for the second/third time: Gives a light blue screen with either the same Remote Desktop warning or an altenate dialogue: "Local Session Manager service failed the sign-in. The number of connections is limited... all are in use...Try later..." After 2-3 minutes the system proceeds to the login>desktop. *If not acknowledged wby clicking okay, the system eventually loads.

    Some Hyper-V enhanced session configs/results:
    Server on/Guest on = Dialogue for 1366x768>>login>RemoteDestopError, if Resolution dialogue is okayed get clear 11366x768 resolution, if outwaited = unclear 1024x768
    Server off/Guest off = No RD message , but slower login (more circling dots) and lower res/unclear 1024x768 VM window. Guest OS can be restarted.

    I also tried other enable/disable configurations such as performing the original install custom.ISO with different Enhanced Session Modes and got several variations of the same themes. Once with the initial intall performed in a Hyper-V already configured with Server=Off, Guest=on I saw no install>autorestart, but upon VM TurnOff>restart Cortana surpised me be saying "Hi, Getting Devices Ready after login", then no resolution dialogue, no RDS message, but guest OS could shutdown.

    So, I'm stuck at my initial questions at top, and wondering if this is possibly normal and I need to simply disable/change some host machine Remote Desktop setting (and have correct Enhanced Sessions Modes) before making custom.wim?

    Any help would be sincerely appreciated!

    P.S.For reference, my hardware is a brand new factory fresh Clevo P650HS-G laptop (i7-7820HK/GTX1070/64GB RAM) running Windows 10 Creators edition (1703). The only system changes were the installation of Macrium Reflect to create a couple MRIMGs, and the installment of ADK (1703) Deployment Tools before creating the customized Win10 ISO. All of my files are on Windows(C:), but Data(D:) holds the extracted Microsoft ISO and is used to save custom install.wim. The computer hasn't been allowed internet access yet, all files have been manually transferred via USB.
      My Computer


  9. Posts : 4
    Windows 10 (1703 build 1506)
       #278

    custom.ISO with 'remote desktop' issue (addendum)


    -- I forgot some pertinent info:
    I directly used the physical machine in Part II and IV; I did not use a VM.
    I may be wrong, but the reason I did this is because I was under the impression that making the custom.wim in a VM would not make an ISO that was 100% identical to my system (i.e. some third party/unsupported drivers, etc. would be swapped for VM compatible components).
      My Computer


  10. Posts : 18
    .
       #279

    Hyper-V not shutting down VM at "Enable System Out-of-Box Experience"


    I'm stuck at 3.8~3.9.

    For some unknown reason my VM doesn't shut down after doing its thang at the "Enable System Out-of-Box Experience (OOBE)" + generalize + shutdown screen/prompt (i'm trying to sysprep a Dutch non-OEM Windows 10 Pro x64).
      My Computer


 

Tutorial Categories

Create Windows 10 ISO image from Existing Installation Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  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 17:03.
Find Us




Windows 10 Forums