Open Windows 10 - SMS Listing doesn't update

I am using the Windows Store app on two different PCs and as far as I can determine, it looks like the SMS conversations listing under the "SMS" tab was created once on first opening, and since then hasn't updated. The messages within each conversation update (including the message preview in the list), but the available conversations, and their order don't change.
I am fairly certain this is the issue, because both PCs have the list in a different state/order from having been linked at different times and haven't budged since.
So I can't speak to people who I started texting to recently, and I've got a lot of useless conversations (like pizza delivery notices) clogging up the list :/

 

Nope, unfortunately.
I just did a few checks:
When opening the android app (phone) & going into "Remote SMS", the list updated correctly.
When restarting the Windows app & going into SMS, i got an error message:

net_http_client_execution_error; The text associated with this error code could not be found.​

A connection with the server could not be established​

at Join!<BaseAddress>+0x9c887c
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at Join!<BaseAddress>+0x6db474
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at Join!<BaseAddress>+0x6f3d14
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at Join!<BaseAddress>+0x6de1bb
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at SharedLibrary!<BaseAddress>+0x54529b
at Join!<BaseAddress>+0x65762d
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at Join!<BaseAddress>+0x64dda9
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at SharedLibrary!<BaseAddress>+0x54529b
at Join!<BaseAddress>+0x91ce64
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at Join!<BaseAddress>+0x64cf4c
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at SharedLibrary!<BaseAddress>+0x39f32f
at Join!<BaseAddress>+0x9329d5
​

Though I think this might have just been a simple network error:
I tried the exact process again, and the list updated without an error. Though the list order is still the same, as described above.

 

To be precise,

The conversations list:

• Shows an "update wheel" upon opening, but the contents do not change.
  
• Does not update its order.
• Does not update the "latest message preview" under the contact name. (Even after opening the conversation and returning to the list)

Inside a conversation:

• The messages update when the conversation is opened.
• All functionality is as expected.

 

Yes, it updated after a brief moment, and displays entirely correctly, in order and with the correct message previews.

 

Nope, sorry :/