Try merging this with your registry. Save it as photo.reg Code: ; ---------------------- Photo-Viewer-Into-Windows --------------------------------------------- ; Change Extension's File Type [HKEY_CURRENT_USER\Software\Classes\.jpg] @="PhotoViewer.FileAssoc.Tiff" ; Change Extension's File Type [HKEY_CURRENT_USER\Software\Classes\.jpeg] @="PhotoViewer.FileAssoc.Tiff" ; Change Extension's File Type [HKEY_CURRENT_USER\Software\Classes\.gif] @="PhotoViewer.FileAssoc.Tiff" ; Change Extension's File Type [HKEY_CURRENT_USER\Software\Classes\.png] @="PhotoViewer.FileAssoc.Tiff" ; Change Extension's File Type [HKEY_CURRENT_USER\Software\Classes\.bmp] @="PhotoViewer.FileAssoc.Tiff" ; Change Extension's File Type [HKEY_CURRENT_USER\Software\Classes\.tiff] @="PhotoViewer.FileAssoc.Tiff" ; Change Extension's File Type [HKEY_CURRENT_USER\Software\Classes\.ico] @="PhotoViewer.FileAssoc.Tiff" You'll find other examples on this forum that are longer and add more file associations. I find that if I get these basic ones set than, if i need to, I can right-click other images and will get offered the option to open them using photo viewer.
I seriously suggest you find another method to customize your images because the amount you whine is astonishing. Moreover, this is NOT a thread for my script and is not the venue to use for your "problems." That's why GitHub has an "Issues" tab for users to make posts in.
Thanks, I was looking for a way to do what you propose without having to install any aspect of ADK. Right now I have a copy of all the crucial ADK files (efisys.bin, etfsboot.com, etfsboot.com, efisys_noprompt.bin and oscdimg.exe) in a "Bin" folder next to a command script applying near identical code as you show. Code: SET "oscdimg=%~dp0Bin\oscdimg.exe" SET "Root=%~dp0" "%oscdimg%" -bootdata:2#p0,e,b"%Bin%\etfsboot.com"#pEF,e,b"%Bin%\efisys_noprompt.bin" -u2 -udfver102 "%Root%\LTSB2019.iso" Which works great and is all very cool and what not, but I had hoped there might be a simple 'repackage to ISO' tool that someone has created that doesn't use proprietary applications or need to be installed.
The "second release" of the 1809 is supposed to happen today. It would be wise to wait a couple of hours and download the newest ISO
I wonder what the official source is? All can happen today but not seen one hint from official MSFT sources, only the release of the SDK 17763.138 is somewhat of a clue.
https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-339#post-1481203 All info about 1809 sku's and related stuff: https://forums.mydigitallife.net/th...p-slow-1809-final-build-17763-1-pc-rs5.77945/