As you can see, the box app is not installed. The operating system is "promoting" it as a possible share option. If this not ads, then it is a "suggestion" at least. Not sure that many users will like to see additional icons of apps which they do not have installed there.
true. I hope those new options will work in Creators Update, since they added them to the user interface.
So folks, any thought about SysPrepping? Maybe we could run sysprep from a running Windows on another partition or even on another hard drive?
It is not ad per se. Just as the apps in Start would like you to initiate the install process after new installation. How effectively having additional share icon on the Photo app is debatable. Some might like it because they are using it in their smartphones to share images already while some don't. That is possibly one of the reasons Microsoft left it there as an option.
Tried to do that. Applied install.wim from sysprep to partition, rebooted to it, and it freezes at beginning of installing devices. Wouldn't install in Hyper-V either.
Well I think they did whatever should do but did not explain it well? Anyway it's time-wasting. M$ should release an insider build soon.
Code: DISM /Apply-Image /ImageFile:C:\install.wim /Index:1 /ApplyDir:M:\ /Compact:ON BTW, not first time I have done this. I do have experience, and it has worked before, just not with this build.
Code: dism /capture-image /imagefile:C:\install.wim /capturedir:M:\ /name:"AnyName" /compress:maximum /checkintegrity /verify /bootable Generic. VHDX is mounted in Disk Management.
Where/how did you first install it on\into to be able to go in audit mode, sysprep and re-capture it? Why did you use the /bootable option?
You said, it wouldn't install on a hyper-v, so please tell me where did you install it on to be able to go into audit mode and sysprep and capture it. That tutorial is not really about this topic. Normally you would have to install the windows in a vm using a dedicated piece of raw unformatted disk in your system, at first OOBE screen you enter: CTRL+SHIFT+F3 (to enter audit mode), then you sysprep with the OOBE, generalize and shutdown system checkboxes ticked, and then you capture it to an install.wim.
OK, I used the Hyper-V image which was linked in this forum.. That was fine. I was messing around with it, and deleted all but admin account. I ran cleanmgr /verylowdisk, then the sageset/sagerun flags of same. I then did sysprep, and captured install.wim. Extracted 14986 Enterprise to MSMG toolkit, and replaced install.esd with my newly created install.wim from 15002. I mounted it, inserted Pro key (success!) and integrated .NetFX3.5 (success!) Saved, and unmounted, rebuilt wim, and made ISO. I will say at this point that I did all of this with 14997 with GREAT success. I then tried intalling in Hyper-V, and it froze at Devices stage. I tried it in a VHD, and it also froze at Devices stage. So then I said f*** it.
So, you took a homebrew vhdx of unknown origins, homebrewed yourself a bit more and the result you've used to test? I thought you downloaded the 15002 base-wim ,did what the OP instructed and simply audit/sysprepped/captured it like abbodi asked.