{"id":28649,"date":"2023-02-13T12:20:36","date_gmt":"2023-02-13T11:20:36","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=28649"},"modified":"2023-02-13T12:20:36","modified_gmt":"2023-02-13T11:20:36","slug":"microsoft-365-bugs-in-word-365-release-2301-write-protection-blocks-changes-and-vba-addins","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2023\/02\/13\/microsoft-365-bugs-in-word-365-release-2301-write-protection-blocks-changes-and-vba-addins\/","title":{"rendered":"Microsoft 365: Bugs in Word 365 release 2301 – Write protection blocks changes and VBA AddIns"},"content":{"rendered":"

[German<\/a>]A German blog reader has pointed out nasty bugs in release 2301 of Microsoft Word from Office 365 or Microsoft 365. Read-only files can only be changed after saving them under a different name. And VBA addins can no longer be executed. Would be interesting if other readers can reproduce these errors.<\/p>\n

<\/p>\n

\"\"German blog reader Ingo W. contacted me yesterday by email, because he resp. his customers are quite annoyed by the bugs. Ingo is probably a developer of VBA addins and runs into problems with Microsoft 365. In a mail titled Bug in Release 2301 Word 365<\/em> he wrote:<\/p>\n

Hello Mr. Born,<\/p>\n

I turn to you, because I hope that you have better contacts to Microsoft or rather can put pressure on Microsoft.<\/p>\n

In the last week I have had problems reported by two customers with Microsoft 365 who are using software of mine [a software he has developed].<\/p><\/blockquote>\n

With \"building up pressure\" or with contacts it is such a thing: I have no contacts to Microsoft and build up pressure on a rubber ball – that does not work. I refer an addendum to this post<\/a>, which I've added, after I sent Microsoft a link to a bug description – they act just stupid, I'm done.<\/p>\n

But I put the bug description of the reader here in the blog, maybe other readers have the problem and someone opens a ticket at Microsoft.<\/p>\n

Version 2301 (Build 16026.20146) of Microsoft 365 was released in the Current Channel as of January 26, 2023, as I saw here. But there is no information about Word in the release notes.<\/p><\/blockquote>\n

Changing read-only files<\/h2>\n

The first unpleasant effect is reported about read-only files. The nature of a read-only file is, of course, that you cannot change it. However, if I understood correctly, it used to be that you could open such a document and amend it. Only when saving, Word then demanded a different name for the write protected document. Ingo writes about this:<\/p>\n

First, it is obviously in the current version so that with read-only files no more change can be made until one has saved these files under a new name.<\/p>\n

This annoys me and my customers, because until now we made the changes and then decided if the changed version should be saved at all.<\/p>\n

But this is just annoying: if Microsoft leaves it that way, you can live with it.<\/p><\/blockquote>\n

Well, here you can understand that Microsoft changes the workflow and postulates that changes to the Word document are only possible if the file is not read-only. Whether that makes sense is another matter.<\/p>\n

VBA addins locked<\/h2>\n

But Ingo describes another effect that brings real problems if AddIns created in VBA are to be used with read-only files. For this he wrote:<\/p>\n

But now to a real huge problem:<\/p>\n

At the latest since release 2301 there is a massive bug that prevents addins programmed in VBA.<\/p>\n

If by VBA new files with read-only templates are created or by VBA read-only files are opened or by VBA Word files are inserted into other Word files, it comes to the abort.<\/p>\n

for instance with\u00a0Documents. Open path & filename<\/b><\/p>\n

With one of my customers with the error message: \"A problem was detected by Word\", with another customer with eternal hourglass without error message and with me with the error message 5792 \"The file may be damaged\".<\/p>\n

The same VBA command works fine if the file is not read-only.<\/p>\n

I can reproduce this with a small test document and a macro with one line of code.<\/p>\n

Similarly, with the command \"Documents. Add Template\". If the template is not read-only, everything works as usual.<\/p>\n

If the template is read-only, there is an error.<\/p>\n

Still important: This effect does not occur with empty, freshly created files. However, if you copy texts with your own style sheets into these documents, the error occurs.<\/p><\/blockquote>\n

Ingo had offered me to provide a test file to test this myself. But this makes no sense, because I don't use Microsoft 365 and I don't have it installed (although Microsoft shows me adds to test it, each time I visit their web site). The question to my readers: can anyone reproduce this? Is this only from release 2301, or did it occur earlier?<\/p>\n","protected":false},"excerpt":{"rendered":"

[German]A German blog reader has pointed out nasty bugs in release 2301 of Microsoft Word from Office 365 or Microsoft 365. Read-only files can only be changed after saving them under a different name. And VBA addins can no longer … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,11],"tags":[47,757],"class_list":["post-28649","post","type-post","status-publish","format-standard","hentry","category-issue","category-office","tag-issue","tag-word"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/28649","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=28649"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/28649\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=28649"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=28649"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=28649"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}