And the office, is 2016 verison, it start fine, but getting problem with licence key, i tried to active it again and reinstall but not work
removing wof.sys breaks installing .net via windows features dialog from windows update. so that now stays put. also working on slimming down vmware workstation, slimmed it down so far from 685mb > 382mb can still make machines, take snapshots, access external devices and network.
wof.sys manages the the new compression methods (lzx / xpress4 ands so on) that can halve the footprint of the installation on disk (usually more thanthat). People has spent months to understand how to port it to W7/W8 and you want to remove it from w10? Thanks to wof.sys (wofadk.sys) I have a fully featured w7 Emb installation that takes 800MB of disk space.Yes Sir, less than a common XP installation. In short try to slim down an OS and remove the single most effective file on size reduction isn't really a good idea.
Why? I'm sorry but don't you think is stupid having 4/5 GB of space wasted just to spare 400K or so I'm reading about yor work just because I'm one of them, but my idea of slim and light doesn't include a broken system in a basic feature like a filesystm filter if you don't consider critical a filesystem thing, what's your idea of critical? People installs the OSes to use them, not to say "hey I removed half the files and it still boots!!!" Not exactly what I'm said. It's a compression feature that you can use for the whole OS, for selected directories, or just on data drives. Just like the 20+ years old ntfs compression. And can be applied during the deployment, or on a live system Peraps forget the win95 days when compressing a drive meant killing dramatically the performances. Nowadays an OS on a compressed drive (especially SSD) is actually faster than the uncompressed ones. Just because the CPU power grown way faster than th HDD speed good
metro stuff is not critical, many gui features and utilities aren't critical, even the gui iself isn't crictical given you can use the os with an alternate shell, or just from command line (see server core),but something that prevents to access a supported filesystem IS critical no matter how you put the matter. A good decision taken because a wrong assumption,is still a good thing What has todo a custom image v.s. a batch customization with what were discussing? Something that shouldn't be touched, shouldn't be touched no matter if you do that properly using dism or using a batch. Usually operating with the tool offered by the OS is better, but there are exceptions, see wmc from Abbodi v.s. wmc from T-S, the former uses dism, the latter uses batches. The former is cleaner, but the latter survives to upgrades and updates, then proved to be better at the end of the story. What I do my systems is my business, I just providing a suggestion to what you shared. I like a lot some ideas coming from your project, and I like to see you spent a lot of time to figure out how to fix things. I like less some other choices like the massive use of permission messing, You should really consider something llke nsudo, leaving the permissions as they are. In short nothing personal, just some feedback as you asked just few messages earlier
Can you please describe how to got that working? Did you manage to make a Windows 7 image wimboot like Windows 8.1 or boot a Windows 10 style compact layout?
Wimboot is possible but compact mode is way better, same space occupied initially (assuming you use the same compression) butafer the image grows because the updates and new programs the latter can be recompessed per file basis. Whatever you can do (both compact or wimboot) manually using wimlib (see their forums) or more easily using Winntsetup by JFX (see MSFN forums). It works for win7/8/8.1/10 and their embedded or server counterparts, x86 and x64, MBR and UEFI, no matter if traditional installations or native vhd ones.
Examples? Download the v8.8.1 WMC installer by T-S. There's a script called _testrights.cmd just click on it, and the command prompt you'll get will have full rights. Any program or command you launch from that window will be able to do everything.