diff --git a/GBM/Managers/mgrMonitorList.vb b/GBM/Managers/mgrMonitorList.vb
index 5c2850d..98b5122 100644
--- a/GBM/Managers/mgrMonitorList.vb
+++ b/GBM/Managers/mgrMonitorList.vb
@@ -152,6 +152,7 @@ Public Class mgrMonitorList
         sSQL &= "Hours=@Hours, Version=@Version, Company=@Company, Enabled=@Enabled, MonitorOnly=@MonitorOnly, BackupLimit=@BackupLimit, "
         sSQL &= "CleanFolder=@CleanFolder, Parameter=@Parameter, Comments=@Comments, IsRegEx=@IsRegEx WHERE MonitorID=@QueryID;"
         sSQL &= "UPDATE gametags SET MonitorID=@ID WHERE MonitorID=@QueryID;"
+        sSQL &= "UPDATE sessions SET MonitorID=@ID WHERE MonitorID=@QueryID;"
 
         'Parameters
         hshParams = SetCoreParameters(oGame)
diff --git a/GBM/readme.txt b/GBM/readme.txt
index be4f01c..255d119 100644
--- a/GBM/readme.txt
+++ b/GBM/readme.txt
@@ -45,8 +45,8 @@ Linux Only:
 
 Known Issues:
 
-- If one or more Game IDs are changed on one computer and these changes are synced to another PC sharing the same backup folder, the local backup manifest data for the changed game(s) on that PC will be reset.
-	- This is intended behavior.
-	- If "Backup Handling" options are enabled in Settings, GBM will see any backups for the changed game(s) as new and will handle them accordingly.
-	
+- If one or more Game IDs are changed on one computer and these changes are synced to another PC sharing the same backup folder:
+	- The local session data on that PC for the changed game(s) will be lost.
+	- The local backup manifest data for the changed game(s) on that PC will be reset.  GBM will see any backups for the changed game(s) as new and will handle them accordingly.
+
 The entire version history of GBM releases is available at http://mikemaximus.github.io/gbm-web/versionhistory.html
\ No newline at end of file