Win10XPE - Build Your Own Rescue Media [2]

Page 32 of 32 FirstFirst ... 22303132
  1. Matthew Wai's Avatar
    Posts : 6,450
    Windows 10 Home 20H2
       #311

    I am now running Win10XPE created via "Win10XPE_2019-11-20.7z".

    Win10XPE - Build Your Own Rescue Media [2]-image-1.jpg

    The committed memory is 6044 MB.
    Assuming the committed memory is "pagefile.sys", where is it on Win10XPE? It does not exist on "RAMDisk (B:)", "Boot (X:)", and "WINDOWS PE (Y:)", while "C:\pagefile.sys" is 960 MB in size.
      My Computer

  2. Kyhi's Avatar
    Posts : 3,728
    Windows 3.1 to Windows 10
    Thread Starter
       #312

    Matthew - where is the OS loaded - as the space you see on X is the cache (Available Space)
      My Computer

  3. Matthew Wai's Avatar
    Posts : 6,450
    Windows 10 Home 20H2
       #313

    Do you mean the committed memory is on "Boot (X:)"?

    Win10XPE - Build Your Own Rescue Media [2]-boot-x.jpg
      My Computer

  4. Kyhi's Avatar
    Posts : 3,728
    Windows 3.1 to Windows 10
    Thread Starter
       #314

    yes you have the loaded boot.wim (OS) plus the free space - if you notice the status bar is empty - meaning it is not reading the space used by the OS
      My Computer


  5. Posts : 2
    Windows 10 Professional
       #315

    internethandle7 said:
    Hi all,

    Sorry for the newb question, but I’m having some trouble parsing how to go about doing this: I use an external audio device/sound card that is connected via USB and has no drivers of its own, relying instead on Windows’ native USB Audio 2.0 drivers (“usbaudio2.sys”). Win10XPE completes my ISO build (with the Audio support box checked) and seems to contain the older “usbaudio.sys” (no “2”), but I seem to be unable to get it to include and install the 2.0 drivers, and therefore my audio device is not working. I have tried the “copy drivers here” integration option via manually pasting usbaudio2.inf from another install, but that seems to have no effect and usbaudio2.sys still fails to show up in system32\drivers or elsewhere after building an ISO and launching from USB drive. I have also attempted to point Device Manager in WinPE to the same INF but Windows then complains that the driver is appropriate for the device but not digitally signed (it also describes it as “third-party”).

    Any help would be appreciated, and thank you to those who so diligently support this forum and project for those of us less knowledgeable!
    As a follow up to potentially help others, I managed to figure out my issue: firstly, my host OS was a very old version of W10 prior to the introduction of usbaudio2.sys, so I was copying and pasting from the FileRepository of a newer version’s install on another drive into the driver integration folder of Win10XPE. More importantly, though, I did not follow instructions very well and was only copying and pasting the usbaudio2.INF file into the driver integration folder. When I pasted the whole usbaudio2 folder in FileRepository from an up to date W10 install as host OS into the driver integration folder, DISM successfully integrated the driver and WinPE associated and installed the drivers for my device upon rebuilding the ISO.
      My Computer

  6. APT38's Avatar
    Posts : 289
    W10, W7
       #316

    GIMP 2.10.28 updated scripts
    TeraByte Image for Windows 3.47 updated scripts

    see post #4 for scripts
      My Computer



 
Page 32 of 32 FirstFirst ... 22303132

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




Windows 10 Forums