![]() ![]() It seems that as Microsoft continues to make changes to their OS (e.g. Apparently those additional ones (2 - 4) helped to eradicate this same issue months ago but had no positive impact for us now. After your suggestion, we spoke to the VMware tech support rep who worked with VMware engineers originally on this issue (months ago) and he recommended appending exclusions 2 - 4 (below) as well. However, adding your exclusion to the snapvol.cfg did. Unfortunately, re-registering the and appX packages did NOT fix the problem for us. ![]() TechGuy129 is our hero!!!!! Thank you for the speedy suggestions! ![]() This corrected the problem, therefore allowing us to successfully update the June MS patch that previously broke profiles, but here we are again with broken taskbars after the July MS Windows Updates of the same Windows feature release (1607). Therefore, we tested not applying any customization especially the VMware optimization tool. It seems that once any customization/optimization is done, irreversible damage takes place leaving profile that log in vulnerable to breaking during some windows update in the future. Also, not all updates break the Taskbar features we went months without issue earlier this Spring. If existing profile Tasbar features work after this, then we conclude the problem has been resolved (which is what we thought in June, but it came back after July updates). After profile is created from the OS, we perform a Windows Update on the Golden Image, then recompose, then try logging existing profiles into the updated OS.
0 Comments
Leave a Reply. |