Skip to main content
Brand User

634 Messages

 • 

50.3K Points

Wed, Feb 20, 2019 8:21 PM

Closed

Sitebuilder Desktop Fix

We have some good news to share with our Sitebuilder Desktop customers! We found that the latest version was not compatible with the most recent updates, as a result we've made available a version that currently functions.

Even though the connection has been reestablished, we do highly recommended making a transition into Website Builder. The Desktop Software has not been updated for several years which means at any time this could possibly become an issue again. Any updates going forward will be focused on improving the new Website Builder experience for our customers.

Below are the instructions to obtain and install the working version assuming you are on Windows 7 or later:

  1. Install/repair Microsoft J# 2.0



  2. Using Windows control panel, uninstall Homestead Sitebuilder



  3. Use Windows explorer to locate the folder c:\program files(x86) and delete the folder Homestead.



  4. Locate the hidden folder c:\programdata. Inside the program data folder, rename the Homestead folder to Homesteadbackup.



  5. Log into your Homestead account



  6. Go to the Websites manager page



  7. Click the Download Sitebuilder link under the edit site button.





  8. Scroll to step 3 under the Troubleshooting section and click the indicated link





  9. Save the program to your hard drive



  10. Open your downloads folder and extract the files from the zip folder.



  11. Run the program SiteBuilderSetup.exe



  12. Log into desktop and select a site. Since you renamed the folder that contains the site files, desktop will download the published site. Then you can test publishing. I have not yet tried to rename the backup folder so this step is not necessary, so I advise you let Sitebuilder create the folder and download your sites.



  13. Try to publish a change and let us know if it worked.

This conversation is no longer open for comments or replies and is no longer visible to community members.

Responses

No Responses!