Announcing Windows 10 Insider Preview Build 16193 PC and 15213 Mobile Insider

Page 8 of 20 FirstFirst ... 67891018 ... LastLast

  1. wen
    Posts : 273
    WINDOWS 10 PRO INSIDER PREVIEW
       #70

    Please HELP Me !! Tried over a dozen "fixes"
    Announcing Windows 10 Insider Preview Build 16193 PC and 15213 Mobile-failures.jpg

    I found the FIX !!
    Announcing Windows 10 Insider Preview Build 16193 PC and 15213 Mobile-fix.jpg

    Update loaded fast with no problems. This "fix" really works. New Build running clean, fast, no bugs (yet) and Outlook 2016 is "perfect", as it should be. I am Very, Very Happy !!
    Last edited by wen; 13 May 2017 at 05:35. Reason: Update
      My Computer


  2. Posts : 573
    Windows 10 Pro 19043.1081
       #71

    fdegrove said:
    Hi,



    The drive letter is only assigned by the OS after it's been booted so yes, not assigning a drive letter to the raw partition is the way to go.
    The method described has been around for decades and still works fine. The only trouble I recall is it would either boot off one or the other (often the last installed) and required either a bootmanager or editing the boot menu.

    But sure it can be made to work and it is a clean install for sure.


    Cheers,
    Hello,

    I have checked the bootmanager and boot menu issue you mentioned and from what I was able to see this is no longer an issue. I was able to boot into my three other boot menu entries (Windows 14393.1198, Windows 15063.296 and Macrium Reflect System Recovery) without any issue.

    My intent when I made the post was to share with other members the fact that there is at least one other way to install Windows from a mounted ISO.

    Kari said:
    @waltc, you cannot clean install from mounted ISO. Only in-place upgrade is possible.

    To clean install you have to boot PC from install media (USB / DVD), alternatively boot from WinPE media and apply install.wim (or install.esd) with DISM, or boot from WinPE media and launch Windows setup from a hard disk partition (or USB / DVD).
    Whether this procedure that I outlined results in a clean install is still not totally clear to me. I doubt that MS would call it a clean install. That is why I went back and edited my original post. I am going to call the procedure I outlined a fresh install. People can call it whatever they want. It is what it is. I think the true sense of the term "clean install" gets lost in the semantics. But, man it sure acts and feels like a clean install.
      My Computer


  3. Posts : 2,826
    Windows 10 Pro X64
       #72

    Hi,

    My intent when I made the post was to share with other members the fact that there is at least one other way to install Windows from a mounted ISO.My intent when I made the post was to share with other members the fact that there is at least one other way to install Windows from a mounted ISO.
    Yes, sure. It's a good idea which will serve its purpose for some I'm sure.

    doubt that MS would call it a clean install.
    It is by all means a clean install. One with a twist but who cares ?

    And thank you for bringing it up, it may be usefull to some of us.

    Cheers,
      My Computers


  4. Posts : 1,261
    Windows 11 (22581.100)
       #73

    WOT said:
    All Macrium Reflect users:

    Check to make sure your USB recovery drive still boots from UEFI. I have a Macrium Home rescue USB drive and a Pro rescue USB drive and they both failed to boot from UEFI (but they worked on 16188). So, I tried recreating them and they still failed to boot from UEFI.

    The temporary fix is/was to turn off secure boot in both my Home and Pro machine and now they both boot properly from UEFI.

    I'm not sure if this is a Macrium issue or the Win PE version that Macrium uses to create the rescue drives.

    In any event, you can also just leave secure boot enabled and then use the legacy boot option (if available) to get to the recovery menu until this gets fixed.
    Thank you, turned off the Secure boot.
      My Computers


  5. Posts : 573
    Windows 10 Pro 19043.1081
       #74

    LEOPEVA64 said:
    I had no idea of ​​this method, excellent, many times I wanted to install from scratch in another partition and the only way I found was to burn the ISO, thank you very much.
    You are welcome.

    fdegrove said:
    Hi,



    Yes, sure. It's a good idea which will serve its purpose for some I'm sure.



    It is by all means a clean install. One with a twist but who cares ?

    And thank you for bringing it up, it may be usefull to some of us.

    Cheers,
    You are welcome.

    Thanks to @meebers and to @AndreTen



      My Computer


  6. Posts : 1,983
    Windows 10 x86 14383 Insider Pro and Core 10240
       #75

    You can apply with DISM (or IMAGEX) from any functional install.WIM (.ESD) to a clean formatted partition (x:) from within a running Windows 10, 8.x or 7 installation and add the applied volume to the Boot menu with BCDboot x:\windows​. You can also remove the current boot menu entry with BCDEDIT so that only the newly applied volume will boot.

    Then all that is needed is to remove (or format) the old Windows volume after rebooting.
      My Computers


  7. Posts : 17,636
    Windows 10 Pro
       #76

    For me, word Clean in clean install refers to primary OS on a clean disk, to start fresh with partitioning options. Wipe the disk and clean install.

    It's true that running Windows Setup from ISO, be it self made, a WIM based ISO Microsoft offers to Insiders, or ESD based ISO made with Media Creation Tool has an option to delete everything and reinstall Windows but this option does not include partitioning options as a pure clean install does.

    It is also true that you can install or deploy additional Windows to dual / multi boot system in addition to primary OS from mounted ISO. This, of course, is also a clean install but not in same sense.

    OK, that now being said, booting my machine this morning my screenshot tool Screenpresso notified me about an update. Accepting it the installer told it needs to download .NET Framework 3.5:

    Announcing Windows 10 Insider Preview Build 16193 PC and 15213 Mobile-image.png

    This seems not work in 16193, WU failing when trying to install feature:

    Announcing Windows 10 Insider Preview Build 16193 PC and 15213 Mobile-image.png

    The error is shown also when trying to add .NET Framework 3.5 from Add or remove Windows features.

    If you face the same issue, a legacy Win32 app requiring version 3.5, just mount Windows ISO (16193 in this case), open an elevated Command Prompt / PowerShell, and run following command to install 3.5 manually replacing drive letter with actual letter for your mounted ISO. In my case Windows 10 build 16193 ISO was mounted as drive H:

    Dism /online /enable-feature /featurename:NetFx3 /All /Source:H:\sources\sxs /LimitAccess

    This installs .NET Framework 3.5 without issues:

    Announcing Windows 10 Insider Preview Build 16193 PC and 15213 Mobile-2017-05-13_10h02_43.png

    I was now able to update Screenpresso.

    Kari
      My Computer


  8. Posts : 17,831
    Windows 10
       #77

    Warning


    Do Not use "Old/New Explorer" by 'Tihiy' on this Build!

    Announcing Windows 10 Insider Preview Build 16193 PC and 15213 Mobile-oldnewexplorer_1.png

    You may experience no access to files or folders whatsoever!
    Last edited by Edwin; 13 May 2017 at 10:46.
      My Computer


  9. Posts : 3,245
    Windows 10 and windows insider
       #78

    Edwin said:
    Do Not use "Old/New Explorer" on this Build!
    You may experience no access to files or folders whatsoever!
    I'm using the Explorer that came with this build. No problems viewing/accessing files and folders. Don't know what you mean by OLD/NEW???
      My Computer


  10. Posts : 17,831
    Windows 10
       #79

    magilla said:
    I'm using the Explorer that came with this build. No problems viewing/accessing files and folders. Don't know what you mean by OLD/NEW???
    'Old/New Explorer' utility by Tihiy, I've edited my original post.
      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 14:57.
Find Us




Windows 10 Forums