![]() So the final implementation is up to you, Lego. ![]() However, komm has a similar warning in his KUC app, and also McRip says that in some cases LDR mode is suffice to remove those issues. I really don't know if such an approach is very hard to implement or not, probably it would be simpler just to remove it with a warning, since it's NOT an important windows update. Press YES to remove it or NO to keep it and install it via LDR mode.'' This warning should be ideally smth like: ''This update can generate explorer issues if integrated / installed. SCCM 2012 R2 Hello, I need to injet KB2685811 into my existing Windows 7 OSD I see that I have it downloaded and deployed under All Software Updates. So, since McRip hasn't yet decided to move these updates to an Additional folder or not, and they are still in the main folder, please include a warning when these updates are beeing integrated (AIO) or installed (Update Installer Tool) via Win Toolkit. Ok, after some further testing I can say for sure that at least on one hardware configuration KB2685811 and KB2685813, if installed in GDR / LDR live system, or integrated in GDR / LDR mode, generates explorer issues.
0 Comments
Leave a Reply. |