Carl Webster Accessibility Statement

Carl Webster is committed to facilitating the accessibility and usability of its website, carlwebster.com, for everyone. Carl Webster aims to comply with all applicable standards, including the World Wide Web Consortium’s Web Content Accessibility Guidelines 2.0 up to Level AA (WCAG 2.0 AA). Carl Webster is proud of the efforts that we have completed and that are in-progress to ensure that our website is accessible to everyone.

If you experience any difficulty in accessing any part of this website, please feel free to email us at info@carlwebster.com and we will work with you to provide the information or service you seek through an alternate communication method that is accessible for you consistent with applicable law (for example, through telephone support).

  • Documentation Scripts, Windows 10 Anniversary Update, PowerShell Version 5.1 and Broken Cover Pages

    August 26, 2016

    PowerShell

    After receiving reports that Word 2016 Cover Pages were not working for any of the documentation scripts with Windows 10 Anniversary Update and PowerShell Version 5.1, I finally did some testing. This is what I found after several hours of testing:

    • Windows 7 SP1, PowerShell versions 3, 4 and 5 all work with Word versions 2010, 2013 and 2016.
    • Windows 8.1, PowerShell versions 4 and 5 all work with Word versions 2010, 2013 and 2016.
    • Windows 10 prior to AU, PowerShell version 5.0 works with Word 2010 and 2013.
    • Windows 10 AU, PowerShell version 5.1 no version of Word works.
    • Word 2016 is not working on any Windows 10 release.

    This is only for the Cover Page. Everything else in the Word/PDF report works.

    I have only tested the en-US cover pages. I am assuming the other ten languages the scripts support have their cover pages broken also.

    I have no idea how to fix the Cover Page. The code came from Jeff Hicks back in late 2012 and has not been touched since. I have reached out for help, so maybe someone who understands comObjects can help me out.

    Maybe the PowerShell team inadvertently broke something with comObjects with PowerShell version 5.1 (specifically 5.1.14393.82) . Maybe I can hope they issue a fix.

    It would also be great to figure out why Windows 10, all releases, broke Word 2016 Cover Pages. Maybe Jeff Hicks will see this, and maybe he knows the answer(s).

    Bad Word 2016 Cover Page
    Bad Word 2016 Cover Page

    Thanks

    Webster

     







    About Carl Webster

    Webster is a Sr. Solutions Architect for Choice Solutions, LLC and specializes in Citrix, Active Directory and Technical Documentation. Webster has been working with Citrix products for many years starting with Multi-User OS/2 in 1990.

    View all posts by Carl Webster

    Comments are closed.