When Framework 4.7 was first released , i downloaded NDP47-KB3186497-x86-x64-AllOS-ENU.exe , extracted this file with 7zip and "Windows10.0-KB3186568-x64.cab" file was among the extracted files.. I have been using this Windows10.0-KB3186568-x64.cab package (314 MB) for integrating Framework 4.7 to 1607 so far. Now, Microsoft released a new package KB3186568 (67 MB) for Framework integration to 1607 Which package will be better for integrating Framework 4.7 ?
Thank you Enthousiast and Abbodi1406 ; Which one takes less time for integrating , compressed or non-compressed , do you have any idea ? abbodi1406 , it is nice to see you here again , you havent been here for a long time
Thanks for notifying. Yes, it works now. I tested at least on 1 real PC which I had the error on it before. We were lucky, seams M$ fixed their issue.
Noticed that the new cumulative update for 1703 also adds the hwexclude thing to x86 like it was doing to x64 on boot.wim (boot index) Still going to be integrating for quite a while, but I'll update if it needs to do the takeown/replace thing on the txt files
I'm not entirely sure why the x64 previous thing didn't work. It had the same hwexclude and hwinclude files added. Perhaps they didn't add virtual machine hardware identifiers? I've just begun testing. I'm sure I'll find out any minute if there's a problem. Edit: No errors during x86 boot setup. Will update when I get to x64 setup. Hopefully they fixed the problem. Edit2: No errors during x64 boot setup. I'm using vmware workstation pro 12.6 If anyone encounters errors with boot setup using the integrated files from KB4022725, please let me know.
With all my W10 installs I create a Recovery using scanstate, Sysprep/generalize & capture. When I deploy this image I re-enter Audit, do my testing, sysprep to oobe, login as normal user. If this works I Reset the PC then shutdown when at Oobe. With build 15063.413 Reset is failing. I've tried it on 2 different PC's. Has anyone else tried Reset?? Note I see 15063.413 has fixed some start menu issues if you re-enter Audit mode...