Our final tests with Windows 10 Version 1709 (Fall Creators Update) revealed timing issues with the local file system, which may lead to changed application behavior as well as application runtime errors. In fact, all coding patterns which first delete a file on the local storage and then assume the file is gone may fail. This is valid for all programming languages used as the behaviour is introduced on the Windows API/file-system level. In other words, an FErase( "test.dbf" ) may lead to File( "test.dbf" ) == .T. in some but not all cases.
With that finding in mind we can not recommend updating production systems right now to Windows 10 Fall Creators Update. Our lab is working to get an idea if there is a way to fix or work around this behavior. For more details see PDR 6954.
By the way: all this reminds us about the infamous SMB2 design bug for which Alaska Software provided a fix on the Workstation side, which was downloaded by tens of thousands of Clipper, Visual FoxPro, Access and Office developers worldwide.
Resumindo:
Na nova versão do Windows 10, pode avisar que um arquivo que foi apagado ainda existe, além de problemas de tempo de resposta, chegando a gerar run-time error.
Comentário:
eu lembro que tive algo assim no Windows 7, mas o recurso de configurar o Windows que está incluso nos fontes do Harbour resolveu a questão.
Não sei se é o mesmo problema, ou se é um problema novo.
Apenas repassando, pra já servir de precaução caso aconteça algum problema parecido.