The Ultimate Windows 10 Image - Chris Titus Tech
video description
Date: 2022-03-21
Related videos
Comments and reviews: 10
David
A couple extra tips you should try which will save you some steps. The last part of this video about modifying the ISO with AnyBurn to add the Autounattend.xml will not be necessary. Try this ... First Tip: Navigate to the --MSMG program folder-\Mount\DVD- folder. This is where you copied the files from the original ISO media. Copy your AutoUnattend.XML to the root of this folder where the setup.exe is located. MSMG will be reproducing this same folder into a new ISO when you select it from -[6] Target- which will include your AutoUnattend.xml file.
Second TIP: This is similar to, the first tip. When MSMG creates the final ISO file, it recreates an identical copy of the --MSMG program folder-\Mount\DVD- folder except that the -.\Sources\install.wim- file (the original standard Windows setup image) file is replaced with the copy that you customized using MSMG. Once you have selected the source media in MSMG (-[1] Source-) and mounted it, you have the opportunity to add files to the installation which will be added later to the target machine during installation. For example, you can add files to a folder called -C:\PostOOBE- and then have a command in your AutoUnattend.xml that will run -C\PostOOBE\MyCustomSetup.bat- the first time the computer reaches the Windows desktop. Personally, I have a whole structure of subfolders with programs, drivers, and custom configuration scripts that get kicked off by a single script that launches from my AutoUnattend.xml. This completes my customized setup image after the Windows install.
To add files to your customized ISO setup, you need to do so before you save your changes in step -[5] Apply-. Navigate to the mounted subfolder located in --MSMG prog folder-\Mount\-. There might be more than one folder mounted depending on whether or not you chose to mount the WinPE boot and Recovery images also. (NOTE: Mounting an image simply unpacks a copy of the original -.\Sources\install.wim- file to a folder which gets customized by the MSMG tool (or other tools that it runs). The mounted Windows Image will be under a subfolder called -Install- within the Mount folder. Drill down the subfolders until you reach the location where you would like to add your files. Note: Once you see some folders that you are familiar with like -\Windows- or -\System32- you will have an idea of what level you are currently at in relative to the root of the drive. For example, if you see a folder called -Windows- then you know that the current folder that you are in is at the same level of where the Windows folder would be located when installed on your computer. That means that the current folder would be most likely the -C:\- root of the system drive because the -Windows- folder is typically in -C:\Windows-.
Finish adding your files and then finalize your customized image in MSMG with Step 5 to save your work, and then Step 6 to create your new ISO. NOTE: If you add a lot of files then your final ISO will be much larger than the original Windows ISO. Mine was 14GB but again, it contains my entire custom image that supports all of our company computers. My files include drivers which I install after Windows setup unlike those that are integrated like this video shows. Try what's best for you. Maybe it is better to integrate the drivers that you can so they are available on the first time you reach the desktop; however; you cannot do that with drivers that have or require additional software and tools. In this case, automate the driver installers and then add them as a post Windows setup step. There are many videos and articles on how to automate software to run silently and you can also use batch files with the built in Windows tools (Powershell, PnpUtil.exe, etc.) Enjoy!!!
reply
A couple extra tips you should try which will save you some steps. The last part of this video about modifying the ISO with AnyBurn to add the Autounattend.xml will not be necessary. Try this ... First Tip: Navigate to the --MSMG program folder-\Mount\DVD- folder. This is where you copied the files from the original ISO media. Copy your AutoUnattend.XML to the root of this folder where the setup.exe is located. MSMG will be reproducing this same folder into a new ISO when you select it from -[6] Target- which will include your AutoUnattend.xml file.
Second TIP: This is similar to, the first tip. When MSMG creates the final ISO file, it recreates an identical copy of the --MSMG program folder-\Mount\DVD- folder except that the -.\Sources\install.wim- file (the original standard Windows setup image) file is replaced with the copy that you customized using MSMG. Once you have selected the source media in MSMG (-[1] Source-) and mounted it, you have the opportunity to add files to the installation which will be added later to the target machine during installation. For example, you can add files to a folder called -C:\PostOOBE- and then have a command in your AutoUnattend.xml that will run -C\PostOOBE\MyCustomSetup.bat- the first time the computer reaches the Windows desktop. Personally, I have a whole structure of subfolders with programs, drivers, and custom configuration scripts that get kicked off by a single script that launches from my AutoUnattend.xml. This completes my customized setup image after the Windows install.
To add files to your customized ISO setup, you need to do so before you save your changes in step -[5] Apply-. Navigate to the mounted subfolder located in --MSMG prog folder-\Mount\-. There might be more than one folder mounted depending on whether or not you chose to mount the WinPE boot and Recovery images also. (NOTE: Mounting an image simply unpacks a copy of the original -.\Sources\install.wim- file to a folder which gets customized by the MSMG tool (or other tools that it runs). The mounted Windows Image will be under a subfolder called -Install- within the Mount folder. Drill down the subfolders until you reach the location where you would like to add your files. Note: Once you see some folders that you are familiar with like -\Windows- or -\System32- you will have an idea of what level you are currently at in relative to the root of the drive. For example, if you see a folder called -Windows- then you know that the current folder that you are in is at the same level of where the Windows folder would be located when installed on your computer. That means that the current folder would be most likely the -C:\- root of the system drive because the -Windows- folder is typically in -C:\Windows-.
Finish adding your files and then finalize your customized image in MSMG with Step 5 to save your work, and then Step 6 to create your new ISO. NOTE: If you add a lot of files then your final ISO will be much larger than the original Windows ISO. Mine was 14GB but again, it contains my entire custom image that supports all of our company computers. My files include drivers which I install after Windows setup unlike those that are integrated like this video shows. Try what's best for you. Maybe it is better to integrate the drivers that you can so they are available on the first time you reach the desktop; however; you cannot do that with drivers that have or require additional software and tools. In this case, automate the driver installers and then add them as a post Windows setup step. There are many videos and articles on how to automate software to run silently and you can also use batch files with the built in Windows tools (Powershell, PnpUtil.exe, etc.) Enjoy!!!
reply
David
Ok this is going to sound crazy. You have Windows bloat, you have Linux bloat. Its built in even after you use all the debloat tools and create custom iso's. When they created windoze and linux for that matter they did so in these high level languages. Now dont get me wrong the idea of natural language programming was a great idea, and everyone seems to have fallen in love with that idea. With their C compilers and other flow chart language flavors of the day bringing their software to market faster and faster creating so many new projects and commercial software that only seems to patch a given problem as a solution. Why not code everything in assembly? I know the arguments. However you would most likely notice that your 16 gb install could shrink to just a couple gigs (mabe) at the most with a whole lot more functionality for the file size given. Not to mention faster execution speed. I know it would be hell to do. Updating would probably not be present as it might be easier to just download a new version of the software. There are many pitfalls to assembly. However alot of the virus, malware and bloat could be less just from the learning curve alone. Do i think everything should be in assembly? No. High level languages do have their place. I just look ar them as devlopment tools in prototyping software process and to achieve a higher level of abstraction. But not in the case of an operating system where assembly could refine the functions of the os.
reply
Ok this is going to sound crazy. You have Windows bloat, you have Linux bloat. Its built in even after you use all the debloat tools and create custom iso's. When they created windoze and linux for that matter they did so in these high level languages. Now dont get me wrong the idea of natural language programming was a great idea, and everyone seems to have fallen in love with that idea. With their C compilers and other flow chart language flavors of the day bringing their software to market faster and faster creating so many new projects and commercial software that only seems to patch a given problem as a solution. Why not code everything in assembly? I know the arguments. However you would most likely notice that your 16 gb install could shrink to just a couple gigs (mabe) at the most with a whole lot more functionality for the file size given. Not to mention faster execution speed. I know it would be hell to do. Updating would probably not be present as it might be easier to just download a new version of the software. There are many pitfalls to assembly. However alot of the virus, malware and bloat could be less just from the learning curve alone. Do i think everything should be in assembly? No. High level languages do have their place. I just look ar them as devlopment tools in prototyping software process and to achieve a higher level of abstraction. But not in the case of an operating system where assembly could refine the functions of the os.
reply
Oskar
Chris can you make a video where you talk about how to increase your android phone battery life(I've just seen the degoogled android phone video), maybe talking about compromises, and way to use the -essential google&others apps-(for increase battery life and maybe fast it up), It would be really nice. Ah and maybe a video where you talk about ios world&ecosystem and android&windows world&ecosystem, and wick one is for who. Your video are always a pleasure to watch, with a ton of new and usefull information.
reply
Chris can you make a video where you talk about how to increase your android phone battery life(I've just seen the degoogled android phone video), maybe talking about compromises, and way to use the -essential google&others apps-(for increase battery life and maybe fast it up), It would be really nice. Ah and maybe a video where you talk about ios world&ecosystem and android&windows world&ecosystem, and wick one is for who. Your video are always a pleasure to watch, with a ton of new and usefull information.
reply
3DDAN
i just think its funny you got off the linux train just as its getting good. you got me to switch, too bad you lost interest it seams. 2021 is an amazing time to be a linux user. im sure you still use linux but from what i understand you have pretty much given up on it. the last thing i needed was vr support on manjaro to finally dump my windows gaming machine and go exclusively linux.
reply
i just think its funny you got off the linux train just as its getting good. you got me to switch, too bad you lost interest it seams. 2021 is an amazing time to be a linux user. im sure you still use linux but from what i understand you have pretty much given up on it. the last thing i needed was vr support on manjaro to finally dump my windows gaming machine and go exclusively linux.
reply
Bala
Adobe Creative Cloud Installer not working. It says 'This Application cannot be installed on your current operating system'.
It seems I removed something in the 'MSMG Toolkit'-Step which Adobe-Installer need.
When installing Win10 as downloaded it works.
Anyone else having this problem or does it work fine with Adobe Creative Cloud?
reply
Adobe Creative Cloud Installer not working. It says 'This Application cannot be installed on your current operating system'.
It seems I removed something in the 'MSMG Toolkit'-Step which Adobe-Installer need.
When installing Win10 as downloaded it works.
Anyone else having this problem or does it work fine with Adobe Creative Cloud?
reply
Brett
iam getting a -
Error: 2-
Unable to access the image.-
Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder.-
The DISM log file can be found at H:\ToolKit_v11.1\Logs\Dism.txt
cant install drivers
reply
iam getting a -
Error: 2-
Unable to access the image.-
Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder.-
The DISM log file can be found at H:\ToolKit_v11.1\Logs\Dism.txt
cant install drivers
reply
Andrei
If I put all the drivers from Snappy to the image doesn't it mean that I would be installing tons of drivers that would also weight a tonne and take storage from my system? Like, would they weight 50 gigs or take more time for installation? Really want to know the answer.
reply
If I put all the drivers from Snappy to the image doesn't it mean that I would be installing tons of drivers that would also weight a tonne and take storage from my system? Like, would they weight 50 gigs or take more time for installation? Really want to know the answer.
reply
Accroment
After I export my drivers using powershell can i use snappy driver to install those exported drivers into a new clean win 10 installed pc if yes how? Do i only need to copy the exported drivers folder into the drivers folder of snappy driver?
reply
After I export my drivers using powershell can i use snappy driver to install those exported drivers into a new clean win 10 installed pc if yes how? Do i only need to copy the exported drivers folder into the drivers folder of snappy driver?
reply
Eduardo
MR chris can you pls make a video about config Nvidia settings like , nivia profile inspector and the nvidia control panel, because i have a medium to low end laptop and im getting 60-80 fps in game on valorant , pls help
reply
MR chris can you pls make a video about config Nvidia settings like , nivia profile inspector and the nvidia control panel, because i have a medium to low end laptop and im getting 60-80 fps in game on valorant , pls help
reply
martinperezalfonso
hi chris, is there any faster way to integrate all those drivers from SDI? I format and reinstall windows on a lot of different machines, and it would be nice to have those drivers integrated in the iso.
reply
hi chris, is there any faster way to integrate all those drivers from SDI? I format and reinstall windows on a lot of different machines, and it would be nice to have those drivers integrated in the iso.
reply
Add a review, comment
Other channel videos
