Setting wim image flag is still exclusive to imagex unless dism has it but MS doesn't want us to know its switch
And why shouldn't DISM's documentation get a fleshing-out, and especially on the desktop side? My biggest complaint about PowerShell as a whole is the LACK of documentation on desktop usage - despite it being cross-platform by design, and part of the core-but-optional feature set of even desktop Windows since XPSP2. New with Windows 8 is additions to the HELP documentation (the offline documentation) that specifically cover PowerShell 2.0. However, there still is not an option for a specific WPS shell prompt on non-Enterprise versions of desktop Windows - not even in QuickTask.
Originally Posted by CorporateRAT View Post There's an option in context menu, when you right click on tile. Then for some reason you have a borked ? the options are there, and well documented... as a add feature . Win 8.1.1 Ent x64
Yup, some reported unable to uninstall the "small update", but some reported it could be done, and some reported if they set a restore point, then it is total roll-back. I guess(not sure), if even the "small update" remains, but currentedition reports 9600.16384, then you could install a next update or the final version.
enterprise mode wil wrk after reg tweak right nw only google home page i found diff and on new leak .msu dnt need any tweak
It's possible to Just Integrate the Windows 8.1 2014 updates to Windows 8.1 RTM install.wim and install the OS. It's not mandatory that we should include all the previous Rollup updates for the installation of Windows 8.1 2014 updates. After the update When you run the Windows update, It lists these updates Definition Update for Windows Defender - KB2267602 (Definition 1.165.3692.0) Cumulative Security Update for ActiveX Killbits for Windows 8.1 (KB2900986) Security Update for Internet Explorer Flash Player for Windows 8.1 (KB2916626) Security Update for Windows 8.1 (KB2862152) Security Update for Windows 8.1 (KB2868626) Security Update for Windows 8.1 (KB2892074) Security Update for Windows 8.1 (KB2893294) Update for Microsoft Camera Codec Pack for Windows 8.1 (KB2899189) Update for Windows 8.1 (KB2883200) {Rollup-A (GA)} Update for Windows 8.1 (KB2884846) {Rollup-B} Update for Windows 8.1 (KB2887595) {Rollup-E (November 2013)} Update for Windows 8.1 (KB2903939) {Rollup-C (December 2013)} Update for Windows 8.1 (KB2904266) Update for Windows 8.1 (KB2913152) Update for Windows 8.1 (KB2913270) Update for Windows 8.1 (KB2911106) {Rollup-D (January 2014)} So, I feel It's just enough to include the Rollup updates only with windows 8.1 2014 updates to the windows 8.1 RTM image and not necessary to include all of the previous updates released so far.
I wonder why WZOR insists on those roll-up's being installed prior then? is there a dependency? - 'suppose the hotfix guys will know... TBH.. I feel more comfortable with all rollup's integrated anyway
Yes, I feel there is no dependency for 2014 update, I just included the windows 8.1 2014 update to the wim image and installed the os, the installation went fine was able to use the new features of the Windows 8.1 2014 update later tried the windows update it listed the rollup's.
Although wzor has given the info about integrating the 2014 update to install.wim and winre.wim but no info is there for boot.wim. I tried integrating the updates to boot.wim index1 & index2 but when you try to install the os, it ask for the necessary drivers dialog in the setup like it ask for the AHCI drivers for hdd in the windows setup I will try to integrate the updates only to the boot.wim index1 or index2 will see what's the result will be.
You don't really need them for the boot.wim The only purpose of the boot.wim is to format the disks, apply the index to said drive, and set boot to hw detection phase. I personally swap the boot.wim from earlier builds like the vl update versions, and we'll probably do that when they re-issue them for this update. In the meantime, I'm sure your previous boot.wim will work fine.