Hello there, The legacy usb option should be working now. Regarding the icons i made some changes as well. As you can see i removed the setup.ico in the assets folder, this is due to the rule #1 of this project: open-source. I know that an icon is an icon, but after all its an encoded file and viruses do exist in image files as well. That icon was taken from some internet source by me, most probably is virus free, but the idea is that i want the user to supply that and take responsibility. Now if you put in the assets folder an windows.ico file, your windows hard disk will have an icon too Quite useful for people like me who have 6 HDDs in their rig with 10ths of partitions. Its a neat way of labeling those drives. Will add this info soon to the readme.
Thank you very much for your support and effort. Windows 10 Professional works great on my old FUJITSU-Siemen Lifebook A531 (2012) Installed via legacy option.
Have crafted a new release, here is the changelog: Spoiler: changelog - fixed driver integration and unattend.xml integration - added legacy USB flashing method - new custom icons for the USB drive and windows local drive
I interrogated the Optimize-Offline.psm1 & cannot locate the parameter "miscellaneous" triggering this error?
There is no more "miscellaneous" key in configuration.json, you have newer script, but old configuration.json. Please update your configuration.json to the newest one.
Thank you Whilst I update from each commit, I obviously missed this & now I have used the latest release & all is well.
Hello everyone, first post here. Thank you for continuing working on this wonderful tool. EDITED: Nevermind.
Hello there, I am working on a simple gui with WPF format. Please ignore my commits of the gui as they are simply not to lose the progress and to sync when i switch from desktop to notebook
@gdeliana If I use the (Optimize-Offline.psm1) from your latest commit at Github It errors at this: Though if I revert back to previous commit no problems?
@gdeliana shared he's working on a simple GUI and not to use the latest commits, they are just test commits until he gets the GUI working. Use the latest release.
No problem, any in time feedback is welcome . It helps in speeding up the bug finding Thanks for the help!!
Is the new GUI different from the old GUI? I ran both with everything Select and saw no difference. @gdeliana And I get a 'Failed to disable optional features.' whether I select any or don't select any. Oh, it works with. I forgot to mention that. I tested that first. Code: "WindowsApps": "Whitelist", "SystemApps": "Whitelist", "Capabilities": "Whitelist", "Packages": "Whitelist", "FeaturesToEnable": "List", "FeaturesToDisable": "List", "Services": "Advanced",
The GUI incorporates all the configuration into one place, and is made for more user friendly experience. For the lists it is the same, coz you still got a selection gui when you run the OO script. Here i have implemented also settings restrictions per windows build, meaning you won't see settings that are not meant for the windows build you selected. I don't understand the problem with the features.
I never said it was a problem. I just never knew the difference between the old GUI to the new GUI as it looked the same to me.