diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 26ae95fe..9224f8f8 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -30,7 +30,7 @@ beta versioning for actual release, beta rc1?
 
 do a linux install fresh again here locally to confirm each step is still legit
 
-C:\Program Files\PostgreSQL\14\bin
+metrics is fucked, see client 1 option, fix that before beta
 
 
 
@@ -400,15 +400,6 @@ console.log(parseFloat(localeParseFloat("1,100.9", "nl"))); // Dutch locale: rev
                                              
 
 
-todo: 1 why is pg not setting path when install server so utils in path?
-	it just doesn't, maybe we should put a sample one in windows installs?
-
-
-
-todo: 1 docs for iis pg install showing linux setting for pgdump path should have windows example
-todo: 1 backup that fails writes a zero byte file but does trigger a general backup failed notification
-	Ideally the file should not exist if it's zero bytes to prevent users thinking it's working
-	show as red line in UI ops backup table if bytes is zero 
 
 todo: 2 test notification sent from ops notification settings form should include a link so can test that the link back url is working 
 
@@ -829,3 +820,4 @@ BUILD 8.0.0-beta.0.15 CHANGES OF NOTE
 - API and HELP URL, changed to dynamically determine this rather than store it once initially determined as it would mess up users if server URL was changed after they have been using AyaNova, also fixed issue with developer mode forcing 7575 if port 8080 and localhost
 - updated all docs with example backslash in config.json to include sample specific to windows and linux separately and predominant warning about any backslashes need to be doubled in config.json file
 - updated install docs for windows iis and lan to include windows pg14's dump path in the example and also a block explaining about setting that to the correct location
+- changed installed config.json for windows lan and iis to include a pre-configured pg_dump path assuming pg14 is installed to default location