Dear friend pl dont rename it just see my attached images to AIO DEBLOATER post . name must be $OEM$ as it is after you extract it from zip archive.
its disaster my friend i dont like this way during windows finished install .a windows prompt select all shedulded tasks to delete then i cant move mouse cursor on it.when i click enter windows stay black screen i would run it after windows install complete how about this https://www.w10privacy.de/english-home/
No friend theres no any need to use Autosettingsps tool as group policy tweaks are already in privacy cmd file.
Friend just select all via [Control plus A] on keyboard & then click ok to remove all scheduled tasks . win10 privacy tool already there inside $OEM$ PACK with best user settings no need to use it again .
If your system ia already installed, Privatezilla 0.43.0 (Phoenix) is a handy little tool for checking your settings aand very easy to use Overview: https://github.com/builtbybel/privatezilla Releases: https://github.com/builtbybel/privatezilla/releases
Brother even Privatezilla will also say all telemetry disabled after somebody click on analyze as all reg tweaks are already there inside privacy cmd . No any tool to check for telemetry will show that any tel is enabled on syatem after user will apply only $OEM$ pack from LTSC till 19043. i know that you are already known of this but as a helping hand you are helping him to resolve his queries thats so great of you always
I am very thankfull to a friend who has increased the count of [NO] which was stable as 4 since a year to 5 today, if he or she can answer what went bad or very bad in his or her scenario so that it will be taken under consideration & will be sorted out . [doesnt matter if friend cant change the vote once voted as negative votes let me empower more n more to do more better in this project] without negative responses one must never be known if theres any vulenrability present or any bug is there which is found by negative comment user on the post of same thread. Special Notice : I have Postponned to release May $OEM$ 2021 Pack Release only for MDL till i think 5th of May . Tilll some personal issues got resolved .
i did on virtual environment after clicking OK, screen stay black when i force restart windows prompt for username and password never configured username and password during install pure disaster could u explain on how to install it on fresh installed windows
Dear Friend i cant understand screen stay black as nobody else or even myself ever faced such a problem or else somebody might already post a problem here before you did . it might be due to other tool tweaks you have applied on your offline wim index before adding that $OEM$ Package to your ISO. Edit : You can ask everybody else who has used $OEM$ Package from this thread if they went into same trouble as you faced it upon selection for Powershell UI based Command. Answer to your Re Edit Question : when i force restart windows prompt for username and password never configured username and password during install pure disaster could u explain on how to install it on fresh installed windows // Friend have you even installed Fresh Untouched OS Disk image on any system which will never ask anybody for User Account Creation Just After POST OOBE Process or you are trying to be over smart. its ok i like smart people but over smartness sometimes lead to a trouble which will never get resolved lifetime If there is anybody else who say yes in this world i will quit IT forever
meaning when have clicked OK ,scheduled tasks applet disappears then nothing happen to finish windows installation
Yes after you select all via control plus a then click ok means all scheduled tasks are removed . if you want to see whats going in behind just use -verbose function for that command to see it in verbose mode about powershell command functioning. Next you say & nothing happens next its not ok cuz it must have to execute next powershell called function there after. due to your already serviced iso via other tool everything is happning with you. cant assist you in that case. Dear Friend i already suggested you to use a fresh OS Disk Image & add $OEM$ Pack inside sources then cross check via installation as virtual OS but i am not known what you have done previously with your already serviced OS disk Image before or else i will assist you on that too without thinking of having anything in return as its just a pure Opensource Project. Please dont plan that much hardly to know anything in return as a term passive gathering . just be free mind n directly talk
friend i removed only compenents i did your steps during installation after check and click ok. then nothing happen i cant se that windows finished Installation. i see only black screen. when i restart virtual machine i can see windows but it require username and password that happen only after i copied pack in source folder
friend i removed only compenents // which tool you used to remove components is it AIO Debloater . i did your steps // which steps via which tool aio debloater . during installation after check and click ok. then nothing happen // cant provide solution cuz you used already serviced iso. i cant se that windows finished Installation. // cant provide solution cuz you used already serviced iso. i see only black screen. // cant provide solution cuz you used already serviced iso. when i restart virtual machine i can see windows but it require username and password // Have you used autounattend xml . that happen only after i copied pack in source folder // ok $OEM$ Pack is used in this. // What is your iso build Prior to 17763 or LTSC or Latest 1904x.
i already told you i am using msmg toolkit .then u told me i have only to copy OEM pack into source folder 19043.xxx how to install oem packs after fresh windows installation completed
i already told you i am using msmg toolkit .then u told me i have only to copy OEM pack into source folder 19043.xxx forget about it . it wont work how to install oem packs after fresh windows installation completed
After so many replies to user query even if he cant understand that if he want me to support on any of my project he must use a untouched win10 iso either with debloater or with $OEM$ Pack . Its more then enough for me to support him thatswhy this user is totally ignored from now onwards .
Uploaded & Updated Latest $OEM$ Pack With All Settings Preconfigured Best for me . I D K what will be the user Experience with that . Just Sharing it for Some Pro's Experts to Rectify & Revert me Back if they want to add some additional tweaks to it as according to there consent as well will let me know about any bug they found in this pack. I never Count Myself as Any Type of Competitor to already Going on Projects on our MDL Community in fact i thank devs for there hard work they have done for best user experience. Want to say to Devs of such projects Please dont count me as your Competitor but just well wisher or as helping hand. any misunderstanding between both of us will lead to hard effects on both of our projects which i wont like in any way. even if its irrirtating to you for what i am contributing to MDL please send me a PM so that i will discontinue all my projects & will request staff to remove this thread permanently. Thats all i want to say to devs of projects currently running on MDL for good will of our Community as well as to remain 100 percent trusted resource in this online World of Cyberspace as MDL is & will always be 100 percent trusted Online Resource for User Computing till Internet is Alive. Spoiler: Urgent Special Notice : <<<<<<<<<< I will not be responsible for any inconvenience cause by this $OEM$ Pack to some average Users if they are not upto that level to understand what are the functions used in scripts of Pack as well if they directly apply this pack to there iso without any knowledge of its functions >>>>>>>>>> Edit : I have said all this cuz our MDL Community is more important for me at Priority inspite of my own script projects. Thanks & Regards.