I just installed 20.0 Build 2250 and immediately found an issue: Task changes pertaining to the new items in this build cannot be saved. They're not saved automatically, and if "automatically save changes in the tree of the task items" is deselected, they're not saved if "Save Changes" is manually clicked.
Changes pertaining to other list items are saved--it's just the new items that don't get saved (e.g. "Stored Store Install Information", "WinSAT Traces", etc.).
I'm using RWC under Win10 Pro 1903 x64.
Issue with 20.0 Build 2250
Forum rules
Discussion on the R-Wipe & Clean and R-Crypto software
Discussion on the R-Wipe & Clean and R-Crypto software
Re: Issue with 20.0 Build 2250
Sorry for a long delay.
We need some more info:
* What where the items that couldn't be saved and in which sections?
* I assume you installed the build as an update. What was the previous build?
We need some more info:
* What where the items that couldn't be saved and in which sections?
* I assume you installed the build as an update. What was the previous build?
Re: Issue with 20.0 Build 2250
It seems to be only the items that are new in this build that cannot be saved:
* System's Own Traces > Logs > Windows Biometric Service Events Log
* Installer Traces > Stored Store Install Information
* Aggregate Traces > WinSAT Traces
* Miscellaneous Traces > RADAR Memory Leaks History
Yes, this build was installed as an update. I don't know offhand what my previous build was--I did not plan to need to know this information. But I install every build immediately (I guarantee I am one of the first to do so each time, since I monitor the update page), so it was the build prior to this one which was publicly available. From what I see on the forum, that would seem to be 20.0.2248.
* System's Own Traces > Logs > Windows Biometric Service Events Log
* Installer Traces > Stored Store Install Information
* Aggregate Traces > WinSAT Traces
* Miscellaneous Traces > RADAR Memory Leaks History
Yes, this build was installed as an update. I don't know offhand what my previous build was--I did not plan to need to know this information. But I install every build immediately (I guarantee I am one of the first to do so each time, since I monitor the update page), so it was the build prior to this one which was publicly available. From what I see on the forum, that would seem to be 20.0.2248.
Re: Issue with 20.0 Build 2250
Thank you for resolving this issue in 2252. However, I would appreciate replies in the future.
Last edited by stardust on Sat Oct 12, 2019 4:53 pm, edited 1 time in total.
Re: Issue with 20.0 Build 2250
The best reply to bug reports is fixing the bugs quickly, isn't it?stardust wrote: ↑Thu Oct 10, 2019 10:58 amThank you for resolving this issue in 2252. However, I would appreciate replies in the future. I take my personal time to report issues. If low-effort is the preferred approach, two can play at that game.
I test/monitor/report for a living and do so on my personal time only when I see fit, which is not often.
Re: Issue with 20.0 Build 2250
Indeed. Thanks. Sorry, bad week.