# Updated Rapidweaver 7 Latest Version Will Not Open Anything

**URL:** <https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718>\
**Category:** RapidWeaver Classic\
**Created:** [June 19, 2018, 4:29am UTC](https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718 "2018-06-19T04:29:45Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gordon](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/gordon/32/2641_2.png) [@Gordon](https://forums.realmacsoftware.com/u/Gordon)\
**Post date:** [June 19, 2018, 4:29am UTC](https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718/1 "2018-06-19T04:29:45Z")

</div>

After running the latest security update to High Sierra 10.13.5, Rapidweaver 7.5.5 will not open any project file.

If I double click on either RW 7 **or a RW 7 project** that I was just working with last week, RW 7 starts up and presents the open file dialog box (not the RW custom launch pad) and will not permit me to open any RW 7 project file. They are all grayed out.

If I try to cancel the open file dialog box, it pops backup open again and again, and again, until finally I have to force quit the RW 7 app.

I have uninstalled RW 7 and reinstalled it. I have deleted realmacsoftware plist file. Still no joy.

Updated info: It will open appropriately in another user account on the same computer, so the issue must be in my original user library. Files open fine on my laptop and other Macs.

Updated info: CleanMyMac to the rescue. CleanMyMac has a Uninstaller program that appears to be more thorough and smarter than I am. After allowing it to uninstall RW 7 and associated files, and reinstalling a fresh download of RW 7 I am back in business.

Bug Report: This is the second time I have had this issue. Is anyone else having this issue?

Feature Request: I actually requested this in the RW 7 Beta program, but it still hasn’t been done.  
RealMacSoftware: PLEASE DO NOT AUTOMATICALLY BEGIN COPYING MY RW6 files until I approve where they are being copied to!

---

<div class="post-metadata">

**Author:** ![Gordon](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/gordon/32/2641_2.png) [@Gordon](https://forums.realmacsoftware.com/u/Gordon)\
**Post date:** [June 19, 2018, 5:05am UTC](https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718/2 "2018-06-19T05:05:49Z")

</div>

Ugh, now reinstalling and activating license for all my plugins… again…

---

<div class="post-metadata">

**Author:** ![wirrah](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/wirrah/32/22867_2.png) [@wirrah](https://forums.realmacsoftware.com/u/wirrah)\
**Post date:** [June 19, 2018, 10:49am UTC](https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718/3 "2018-06-19T10:49:50Z")

</div>

I have had this issue a couple of times (Sierra not High Sierra). RW starts and requires a file to open that is not specified and is certainly not a project file. Both times were after a system update and both times were resolved by logging out and in again (or maybe rebooting - can’t remember). It occurred after specifying a different location for add ons but I’m not convinced that was the issue.

---

<div class="post-metadata">

**Author:** ![teefers](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/teefers/32/8173_2.png) [@teefers](https://forums.realmacsoftware.com/u/teefers)\
**Post date:** [June 19, 2018, 12:51pm UTC](https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718/4 "2018-06-19T12:51:03Z")

</div>

> [@Gordon](#):
>
> CleanMyMac

Very good chance that utilities like that are causing the problem to begin with.

> [@Fix “Open” Window Issue in RapidWeaver 7.x on High Sierra](http://forums.realmacsoftware.com/t/fix-open-window-issue-in-rapidweaver-7-x-on-high-sierra/17831):
>
> A few of our users have reported a weird issue in High Sierra where opening RapidWeaver would result in an “Open” window that would render RapidWeaver useless and not let you open a project file (or use RapidWeaver at all). Here’s a [screen grab of what that window looks like](https://www.dropbox.com/s/lb3qoufcf6cu78q/open-issue-rw7.png?dl=0). We’re 95% sure this is a result of using a Mac utility tool (CleanMyMac, MacKeeper, etc). These apps tend to delete important preference and cache files RapidWeaver uses for projects, etc. The simple fix is to delete your…

If you need to uninstall RapidWeaver:  
[https://help.realmacsoftware.com/rapidweaver-troubleshooting/how-to-uninstall-rapidweaver](https://help.realmacsoftware.com/rapidweaver-troubleshooting/how-to-uninstall-rapidweaver)

---

<div class="post-metadata">

**Author:** ![wirrah](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/wirrah/32/22867_2.png) [@wirrah](https://forums.realmacsoftware.com/u/wirrah)\
**Post date:** [June 19, 2018, 8:11pm UTC](https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718/5 "2018-06-19T20:11:49Z")

</div>

Just a follow up. While ‘CleanMyMac’ may be an issue it was not the cause in my case (as I don’t have it or anything similar - my Mac just accumulates dross!)

---

<div class="post-metadata">

**Author:** ![Gordon](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/gordon/32/2641_2.png) [@Gordon](https://forums.realmacsoftware.com/u/Gordon)\
**Post date:** [June 25, 2018, 3:26pm UTC](https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718/6 "2018-06-25T15:26:24Z")

</div>

No, this was not what caused the problem. This is a RW resource location issue. I have replicated it on several cycles of reinstalling RW according to instructions.

Upon a fresh install of RW, without an option to block it, RW senses that I had RW 6 folders still in my library and automatically begins to copy them into Dropbox. Then when I go to RW preferences and try to redirect the resources to my more recent designated folder of themes, stacks, plugins, it wants to automatically (with no opportunity to say no) copy over the RW 6 era themes (into and replacing newer versions of themes) to my preferred location.

I am pretty frustrated with this!

---

<div class="post-metadata">

**Author:** ![teefers](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/teefers/32/8173_2.png) [@teefers](https://forums.realmacsoftware.com/u/teefers)\
**Post date:** [June 25, 2018, 9:44pm UTC](https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718/7 "2018-06-25T21:44:07Z")

</div>

I’m not at my mac right now, but try to starting RW7 will holding down the option key. If I remember it will ask if you want to be prompted to copy files.

---

<div class="post-metadata">

**Author:** ![Gordon](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/gordon/32/2641_2.png) [@Gordon](https://forums.realmacsoftware.com/u/Gordon)\
**Post date:** [June 29, 2018, 1:31am UTC](https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718/8 "2018-06-29T01:31:36Z")

</div>

A week ago after I reinstalled RW 7, on launch it began the copy process again. All of my RW resource files disappeared. I went a week round and round with Dropbox, finally today I went to an old work place to get a physical backup (Dropbox recovery is not all that great.) I tried both the logout, restart, and option key, no joy.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/system/32/25301_2.png) [@system](https://forums.realmacsoftware.com/u/system)\
**Post date:** [July 29, 2018, 11:31am UTC](https://forums.realmacsoftware.com/t/updated-rapidweaver-7-latest-version-will-not-open-anything/20718/9 "2018-07-29T11:31:39Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
