Your work is the Dockerfiles you wrote, not the images that was a by product of your work. All you have to do is a bunch of docker build . commands. You should even have some handy scripts for that…
Your data volumes might not be lost either. They might be in a different directory than where docker is now looking for them, else that’s what backup are for.
If you want this to be seen as an issue or a bug, you should give a few more details like :
Maybe Docker Desktop has created a new virtual hard disk in Hyper-V. Open the settings in Hyper-V manager if you don’t know where to find this folder. First of all, stop Docker Desktop and make a backup of everything you find here. Then, if there is a new and an old hd, rename the new to something else and rename the old to the name of the new. Start Docker Desktop and try again.
I already had some similar incidents and never lost anything, but finally started to believe that it may be a good idea to backup the volumes regularly.
Of course I don’t trust any software (zero-trust-with-exit-scenario).
I still think that @sebt3 is correct and your data is around somewhere. If we speak of your volumes. If you say that your containers have disappeared, this may happen. Containers are volatile and should contain no data.