Forum Discussion
Word random crash during Word mail merges after windows update
Hello, Since the Windows 24H2 BUILD 26100.4652 update, we've been observing a random crash during Word mail merges. These are lists of fields in tab-delimited txt format. These random crashes occur both during the generation of our VB code and during manual testing. The affected machines are those that have received the latest Windows updates, regardless of the version of Word installed (2016 and later). In addition, the crash can occur directly during the merge request, while scanning records, or during the final multi-page generation. Thank you for your help.
7 Replies
- JPJCopper Contributor
The problem persists with build 19029.20156. Windows 11 updated
- JPJCopper Contributor
Thank's xohyx
Despite Windows and Office updates, the problem persists. I've better understood the issue. The crash occurs when carriage return (CR) and only CR (no LF) are contained in one or more tab-separated fields.
Of course every record ends with CRLF.
With few recordings, it works.
Problems appeared with the 18925.20168 build and persist with the latest one obtained 18925.20184
- xohyxIron Contributor
Just roll back recent Windows updates and fix Office.
- JPJCopper Contributor
Thank's xohyx
Despite Windows and Office updates, the problem persists. I've better understood the issue. The crash occurs when carriage return (CR) and only CR (no LF) are contained in one or more tab-separated fields.
Of course every record ends with CRLF.
With few recordings, it works.
Problems appeared with the 18925.20168 build and persist with the latest one obtained 18925.20184.
- JPJCopper Contributor
Thank's xohyx
Despite Windows and Office updates, the problem persists. I've better understood the issue. The crash occurs when carriage return (CR) and only CR (no LF) are contained in one or more tab-separated fields.
Of course every record ends with CRLF.
With few recordings, it works.
Problems appeared with the 18925.20168 build and persist with the latest one obtained 18925.20184
- JPJCopper Contributor
The problem persists with build 19029.20136. Windows 11 updated