Getting back to Earth, I am glad that not everyone has had this problem but some do. I do not use an SSD , all I know is that I have had it and others have as well. The next build may be better.
Remains my view that computer-of-use should run a stable legit and supported OS, with experimental stuff of whatever nature/source confined to other partition(s)/system(s). So far though it seems there are enough ways of 'rolling back' windows to previously functioning version that imho most folks should have a way out of such messes.
The purpose of the Windows Insider Program is to allow people to get access to experimental and pre-release software from Microsoft, and allow Microsoft to get feedback on said software in order to improve it in the future
The software is not production-ready, and can be very unstable. As a result, you may experience occasional crashes and data loss. We are not responsible for such issues, and it is your responsibility to back up your data. By participating in this program, you agree to backup your data frequently. We are collecting data as part of this program, and as a result, your data will be collected according to our privacy policies. In addition, we have the right to automatically update, change or disable the experimental and pre-release software provided through this program.
Microsoft Windows Insider Program Agreement Explained in Plain English - TLDRLegal
TBH if you cant fix it maybe you shouldent be using test builds anyway or trying to use a screensaver at all in first place . (some things work on some test builds and not on others thats the the way it is . )
I dont know anyody * (well almost anybody ) or anybiody on Widows 10 that uses screen savers any more they are so windows 3.1 and Windows 95 and they have had the potential to be problematic on thier own and w/third party screen savers to spread maleware since windows 3.0 anyway .
With all the problems you are having and a lot us aren't I tend to think its a configuration /HDWE/Driver problem or some dodgy software or maleware on your build .
10547 isnt the most stable test build and has some warts thats true but it's useable and it ain't bad like some of the earlier builds . Hopefully you havent done anything foolish like disabling UAC controls and inviting [more] instability .
FWIW The test bulds are free but not finished products you cant expect to call upm M.S. tech suport on a test build that's what the Windows Insider forums are for on thier end .
Y.P. sounds like a simple fix you say you can fix it, why not fix it and let everbody know how thats the usual procedure in a beta test ,is this your first beta test ?
Why would you be using screeensavers in Windows 10 anyway it already has a lock screen and you can change the image on it , it would seem to be inviting problems doing that but to each his own .
FWIW it's not M.S. responsibility to fix the test builds if you read the EULA , RTM might be a better fit for you .
I can't seem to find Install.esd after update was finished, all I found was WindowsOld.wim file
does that mean my chance of making an ISO of 10547 is gone?