Yes, and they use the unparsed (raw) format from tgftp.nws.noaa.gov.
VWS hasn't been maintained in years, and will likely not have any updates since Ed retired.
The underlying issue is that http access to tgftp.nws.noaa.gov is now deprecated (https and FTP still works), but VWS use of https is likely suspect in that its libraries likely use a (now deprecated) old TLS version which is not supported on the newer tgftp service. So, VWS with static code will likely not be able to directly refresh the file in c:\vws\metar again.
What I don't know is whether VWS parses the METAR when it gets it from the internet, or downloads, then parses the file in the filesystem.
If the latter, then having a second process refresh the file contents would work. If the former, then having a new file in vws\metar directory would have no effect.
Maybe it's time to switch to supported weather software -- I can suggest CumulusMX (being actively developed) or weewx (also actively developed) or Weather-Display (still supported, development in suspension).
I, too, run VWS, but not for my primary site (Weather-Display/WeatherLink) -- just to have testing for the Saratoga template VWS plugin.