Bit the bullet with ltsc2019 107 and your Program with a helper. Running well i can post anyway. Thanks for all the hard work always appreciated. Best wishes and season cheers Regards
This is a windows feature. To become a full administrator on a computer, you need to activate the built-in account and work on its behalf. Click "Start" with the right button, you need the item "Command line (administrator)" Type the following command, press Enter net user administrator / active: yes Press Ctrl + Alt + Del and select change user. Log in as Administrator. If you work under this account, you will get full control over your computer.
Awesome, didn't think to do it that way, so thank you. The command I settled on was (ended up wanting Store still): Code: Get-AppxProvisionedPackage -path %MOUNT% | Where-Object {$_.packagename -notlike "*WindowsCalculator*"} | Where-Object {$_.packagename -notlike "*WindowsStore*"} | Remove-AppxProvisionedPackage -path %MOUNT%
I've been testing 1809 on my test-pc since v9.0 came out. Apart from the wake from sleep issue that's been around since 1507, I've not experienced any problems. I just upgraded my sons PC today, and so far no issues. Removed everything except IE and Photo Viewer. I have a 1709 laptop that was created from v8.2, which I was going to reinstall with v8.8 as windows updates are broken and applications regularly hang. Given the lack of issues I've had with 1809 viz v9.0 MSMG, I think I will just go straight to 1809... I'll report back if I have any issues.
Will it support Xbox.TCUI app, Codecs Intel Video, Codecs Video Compression, MPEG-2 Splitter, Sounds, Firewall, Airplane Mode and Radio Management Service, Windows Temporary Files Cache, Shell Hardware Detection, Send to Email and Desktop, Remote Procedure Call (RPC), Embedded Mode, Action Center, Languages/Keyboard Layouts, Windows Mixed Reality, Support directory removal, Manuel feature repository, .NET assembly cache, .NET Framework 2.0, 3.0 and 3.5, Tablet PC, InputApp, User Account Control (UAC) and WinSxS\Backup removal in future versions?
Didn't get an answer to my question I posted for LTSC 2019 (Post #9172), but I think I have it figured out. Looking at the readme in the MSMG distribution I should first remove components then apply updates. Then I should use dism /clean-image /startcomponentcleanup and finally add dotnet 3.5. That sound right? Seems to work fine in my script, reduces the size of install.wim about 320MB. The smaller the better so I don't have to split the image down the road when the cu files get bigger.
Sounds similar, 3.19 GB after integrating about 32 MB of drivers. Only thing I'm adding other than that is dotnet 3.5.
eh.. LoL ^^ you are a customer, a patient, because you deal with this... eh .. os, named windows - without need!!! joke!! simply everyone still relying on this batch of cood of a os is totally insane, hasn't got the right corner. so.. what you "are in", when you disabled uac (you should - it's ms' joke steal your time for various actions ;-) is called "admin approval mode"! this means you frequently have to provide credentials. and this is everything different than easy to.. "mitigate". often you in fact have to be fast. by using prepared links, scripts and so on, but even that was already adressed by microslop, windows is watching your actions all the time, in a number of layers! i erased "system restore" with good results! further there are "shadow copies" windows is using against you, resilient file system 2.0, and i think "MSQM" is one of the most brutal features of windows. admin is nothing.. sorry for posting so much, but i deal with this crap every day i almost destroyed my latest 1809 install. as always, but hiberboot still works and i notice windows is not amused because sysrestore is absent, reason for hope! - - - - - to make this clear, you have to use the septembre image 17763.1 !!! (i am also that dumb, used a dirty image many times) if you do not, component cleanup & resetbase doesn't work, it ends at 20% many times and says everything is fine.... if you use RTM image (17763.1) the process works and takes much longer to complete
May be but I'm not in a hurry to add more components as it will become more difficult for me to manage/troubleshoot.
Yes. If you want to use W81 ADK then you need to modify the script Code: :: Setting WADK tools environment path variables if "%HostVersion%" equ "6.1" set "DISM=%~dp0Bin\%HostArchitecture%\DISM81\Dism.exe" if "%HostVersion%" neq "6.1" set "DISM=%~dp0Bin\%HostArchitecture%\DISM10\Dism.exe" To Code: :: Setting WADK tools environment path variables if "%HostVersion%" neq "10.0" set "DISM=%~dp0Bin\%HostArchitecture%\DISM81\Dism.exe" if "%HostVersion%" equ "10.0" set "DISM=%~dp0Bin\%HostArchitecture%\DISM10\Dism.exe"