Search results

  1. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    Sorry not been around much as I'm pretty much done optimizing my builds, if you guys need my updated gaming optimized XML's, they are all tested here and work (Even use them in multiboot setup) These are pretty much my 'final' builds on any of these windows versions, although I tend to stick...
  2. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    Since that enabled itself after opening store/game, there's a good chance.
  3. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    Everything that is started below 'Workstation' is all the junk that got triggered after I initiate microsoft store / thieves.
  4. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    Dafuq? Isnt that supposed to be part of the driver package? Lunatics.
  5. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    Could be a disabled service? Store is really sensitive to that.
  6. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    Not to mention all the different NTlite build versions which all behave differently. Luckily the version used is in the .xml file :-)
  7. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    Perhaps the 16GB pagefile addressed? Like the title says, its not an 'absolutely minimized' LTSC build as that would indeed break more than it fixes. Whatever runs in memory is still more important than stripping out literally 90% that is not even touched in runtime cases. I can run Sea of...
  8. M

    Updated Windows 8.1 -> Telemetry removal component not removing telemetry executables.

    Hi. Recently processed a Windows 8.1 (Fully updated) build in NTLite, however after the component removal process, with removing telemetry, there is still telemetry going on in the background after an installation. Both Compattelrunner.exe and diagtrackrunner.exe occasionally seem to start at...
  9. M

    'Unload registry failed'

    Nah, it happened even on a reboot. Clean windows. But I couldnt wait as long I just decided to reinstall the VM. Perhaps it was a rare bug with VM? I did use multiple versions on the system, but they were all in their own separate folders. Not sure if it helps. Also it was no issue with the...
  10. M

    Install Windows 7 & 8.1 on Intel 8th, 9th, and 10th generation - Closed

    Fair nuff. Perhaps it will be useful to some. I never used 8.x , guess never really a need for it. I suppose 8 is more like 10, but since 10 has DX12 support and other tweaks under the hood.. Usually run dual boot 7/10 for old skool support :P
  11. M

    Install Windows 7 & 8.1 on Intel 8th, 9th, and 10th generation - Closed

    Main reason why W7 fails on new systems, next to no NVMe/USB3 support(two which are easily remedeed) is the W7 lack of UEFI graphics support, or rather EUFI lacking classic vga/vesa support for it. As soon as Windows 7, be it setup or runtime, loads VGA driver, the system crashes. Same happens...
  12. M

    'Unload registry failed'

    Continuously getting this on the last two (beta) updates. Not sure if related. Already tried unload, cleaning dirs and all sorts, but it just keeps happening. Any idea? :-C Happens on the end of 'removal' when its lit green and 100%
  13. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    Nope :-) I use a script to automatically jump to performance profile when a game runs. A bit messy but it works :-)
  14. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    Theres usually 3 profiles but with new win 10 builds some editions have 'Ultimate' setting. So I default delete Power saver and the old High Performance. Since nobody has ever complained about performance degradation on the new profile or otherwise performance issues, I just decide to remove...
  15. M

    How to remove Win10 1809 Update schedule before Windows load

    New Windows 10 builds have a function where a disabled Windows Update service automagically gets re-enabled and started, I think you'd need to rip out the windows update 'medic' component or whatever its called, which forcibly re-enables update service.. I'm kind of surprised removing the task...
  16. M

    EFS (Encrypting File System) & Appx

    If store and apps are dependent on EFS, i very much doubt it.
  17. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    But the profile already inherits VMWare support and corresponding drivers, or did you take then out/redo profile?
  18. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    I see. Well, could be anything, from different Windows build, different VMWare etc.. Try 3D Accel off or on in VMware perhaps? Since its related to dwm.exe?
  19. M

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

    Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems. [Updated 2020-02-26, will not receive any more updates as I personally went on with Post-install scripts to configure my windows] Version 1.0.5b - Event Channels now fixed...
Back
Top