NW Scheduler/Publisher - Updates, Support, and Suggestions

[Marky]

On 2/17/2026 at 2:14 AM, Gilbert Osei Agyedu said:

In the Congregation>>Groups and Families like this:  

We have always named the groups after the respective overseers. Jones Field Service Group, Johnson Field Service Group, Smith Field Service Group, and so on. This makes it much easier to remember who is with each group than trying to remember numbers. Plus it automatically sorts itself alphabetically.

[Gilbert Osei Agyedu]

Yes! It's a good idea and more descriptive. We have not thought about that. Thanks. 

[Andreaw]

I installed NWS desktop on Windows 11 on UTM (virtual machine).

Now, if I want to install it on another virtual machine, do I have to disconnect from NWS Desktop installed on the virtual machine or UTM?


Inviato dal mio iPhone utilizzando Tapatalk

[Andreaw]

I have a problem with NWS DESKTOP.

 

I installed NWS Desktop on Windows 11 running on UTM (a virtual machine) on my Mac.

 

Now I’ve installed it on another virtual machine using VMware Fusion Pro. After synchronizing everything, it takes me back to the initial login screen.

 

Do I need to configure anything specific on Fusion Pro? I downloaded the latest version of Fusion Pro.

 

[NOTE: I had an AI translate the text this time but please post in English in the future. Thanks!]

[Pastore72]

Hi dear brothers, since the last update I noticed that the tasks that I previously received when they asked me for a territory, now they do not appear to me, if the program is closed, if it is open it seems to me that they remain, this is because today I had opened it and it remained as a task, otherwise I only see the emails, does the same thing happen to you too?

[Cruzer]

Perhaps do NOT update to the latest build, #1431. Tried on 2 separate systems and the "Public Speaker Sharing" feature appears broken. The sync wheel just spins and does nothing. The nwscheduler.com website to report a problem also seems broken. Not able to contact them to report this issue I'm seeing.

 

[Floyd]

I am on 1431 and not having an issue. Maybe it was fixed over the last 21 hours.

 

EDIT: I was wrong. I just updated to 1431 and now have the same problem. I should have listened.

Edited Saturday at 07:30 PM by Floyd

[Cruzer]

On 2/20/2026 at 1:37 PM, Cruzer said:

Perhaps do NOT update to the latest build, #1431. Tried on 2 separate systems and the "Public Speaker Sharing" feature appears broken. The sync wheel just spins and does nothing. The nwscheduler.com website to report a problem also seems broken. Not able to contact them to report this issue I'm seeing.

 

 

I reported this issue yesterday but have not received a reply yet and there is still no new update to fix this. Besides 'Public Speaker Sharing' not working, we also noticed when selecting the 'NW Publisher app' tab in NWS Desktop, there is a single button to 'Reconnect'. It reconnects when selected but will ask to reconnect when opening the program each time.

 

Usually when we open NWS Desktop and immediately go to the 'Updates' section, the area next to the 'Check for Updates' button is blank. After being open for a bit (approx 15+ seconds), it'll switch to, "Checking for updates...". In the latest build however, it immediately says 'No Updates'. Just a few bugs we've noticed. We're currently unable to exchange public speakers.

[Marky]

Are all of the brothers in your congregation that are connected to NWS updated to 8.0 #1431?

[Cruzer]

2 minutes ago, Marky said:

Are all of the brothers in your congregation that are connected to NWS updated to 8.0 #1431?

 

Yes.

[Marky]

Ours appears to be working. Is it possible that the congregation you are trying to share speaker's with does not have all of their brothers updated? I wasn't real clear on what part of the process you are getting the endless scrolling so I am probably way off. Just brainstorming.

[BigMAC]

There is a update out now, 1432. It solved the congregation sharing for us atleast.

I also noticed that they are preparing a another great update.
In the language file i noticed this new text lines:
"Refresh All Persons"
You should only do this if MANY persons are having App data problems or cannot connect

It would be great feature, for some reasons many of you publishers cannot login unless I refresh them in NWS...

Edited yesterday at 09:53 AM by BigMAC
Added som info about refresh all persons

[Floyd]

2 hours ago, BigMAC said:

There is a update out now, 1432. It solved the congregation sharing for us atleast.

 

Confirmed.

[Cruzer]

8 hours ago, Cruzer said:

 

I reported this issue yesterday but have not received a reply yet and there is still no new update to fix this. Besides 'Public Speaker Sharing' not working, we also noticed when selecting the 'NW Publisher app' tab in NWS Desktop, there is a single button to 'Reconnect'. It reconnects when selected but will ask to reconnect when opening the program each time.

 

Usually when we open NWS Desktop and immediately go to the 'Updates' section, the area next to the 'Check for Updates' button is blank. After being open for a bit (approx 15+ seconds), it'll switch to, "Checking for updates...". In the latest build however, it immediately says 'No Updates'. Just a few bugs we've noticed. We're currently unable to exchange public speakers.

 

Build #1432 appears to of resolved these issues for us as well. All our 'Public Speaker Sharing' exchanges appear to of been reset however. Some old denied & cancelled requests even showed up. Will have to go through them all to correct and reapprove the correct ones.

Edited yesterday at 01:10 PM by Cruzer

[molnarj]

3 hours ago, BigMAC said:

I also noticed that they are preparing a another great update.
In the language file i noticed this new text lines:
"Refresh All Persons"
You should only do this if MANY persons are having App data problems or cannot connect

 

It is already there. Look under NW Publisher App section on the right side.

[BigMAC]

5 hours ago, molnarj said:

 

It is already there. Look under NW Publisher App section on the right side.

Aaah now I see. I looked under App persons. 
Thank you!

[Marky]

Not all of our brothers are updated to #1432 yet. Just today, all of our field service meeting times changed from 10:00 to 12:00. No one had even tried to edit anything in there at all - it just changed on its own for no reason. We are going to wait until everyone is updated and then try to change it back.

[Pastore72]

Hi everyone, during our traveling overseer's visit, he presented me with a problem that all congregations using NW have. I'll explain and ask if there's a way to resolve it. When printing the S13 form, according to the overseer, the "Last Completed Date" column should show the last closing date of the previous service year. The other columns are fine, namely assignments and completion.
He's very adamant about this too, and every time we visit, I have to fill out the form manually.
Do you think there's a solution?
Thanks

[BigMAC]

16 hours ago, Marky said:

Not all of our brothers are updated to #1432 yet. Just today, all of our field service meeting times changed from 10:00 to 12:00. No one had even tried to edit anything in there at all - it just changed on its own for no reason. We are going to wait until everyone is updated and then try to change it back.

We have the same problem. Every field service was changed to 00:00. But I changed it back and it have worked since. 

Other problem we had is that the schedule for CO Visit was also changed to 00:00. I changed back and sent to the app and it looks ok in the NWP but after next restart of NWS it's changed neck to 00:00. I have reported this to NW.

[Jonathan1]

From the many responses to this topic, I've noticed that there are numerous versioning issues with NWS and NWP. Especially when schema changes occur on NWS, it's possible that the NWP clients aren't yet on the current version. This can lead to major compatibility issues, such as those reported here.

 

I've solved these versioning issues with Baruch. The environment is updated using versioned messages, ensuring continued compatibility.

 

I've explained how I implemented this in this post. Perhaps it would be a good idea for the NWS developers to implement this same principle as well. It prevents a lot of problems.