Parallels 17 on M1 "Save As" for MS Office defaults to Save in AppData folder

TedM2

Bit poster
Has anyone had this issue? Parallels 17 on M1 "Save As" for MS Office defaults to Save in AppData folder. When I do a Save As in Excel or Word, the default location shows correctly, but when I click on the path, it is actually trying to save in AppData, and it fails. If I go and browse the location I want to save in, it works fine.
 

Attachments

  • Screenshot at Dec 10 17-50-04.png
    Screenshot at Dec 10 17-50-04.png
    80.6 KB · Views: 8
Yes, they found a fix, something deep in the system, but easy. Support should be able to help you. They can look up my ticket.
 
Can you give us your ticket number? Support can't look it up via your screenname. Thank you!
 
[Parallels #3225731] Save As failing in Windows 11

Our development team is working on fixing this issue in future updates.

For now, as a workaround, follow these steps:

1) Create a snapshot to back up the current state: https://kb.parallels.com/en/5691

2) In Windows, locate c:\windows\system32\prl_np.dll and rename it to prl_np1.dll. Copy prl_np.dll from this archive: https://fe.parallels.com/c0283acd496dda9cdd91341ca99175c4/prl_np.zip to the same c:\windows\system32\ location.

3) Reboot Windows and check again.

If the issue still persists, please, collect an additional technical report(click Parallels icon || > Help > Send technical data > check "Attach screenshots..." > press Send Report) and send the report's 9-digit ID in a reply to this e-mail.

Best regards,
 

Attachments

I have been reading this thread. Question I have is do you have the Office apps installed in the Windows VM or are you using the online version of Microsoft 365? Because I generally work with Word and Excel (only two Office apps that I generally use) on the Mac side and when I try to open a document on the Windows VM side it insists that I upload the document to my One Drive account. Otherwise it will open the document with the MacOS version of Word/Excel.
 
When I upgraded to the latest release, the bug returned. Can I replace the file with the same version as above to fix or do I need an updated file?
 
Back
Top