After reinstalling diablo i cant run classic version due to "lack of CD of diablo", pre reinstall works fine - i assume its problem with installation since in cmd (configuration when instal) there is an error (cant show it bcs it dissapear to fast).
An error in game said its a problem with diabdat.mpq - in folder diablo in gog there is a diabdat.mpq (493MB) but in dx folder there is diabdat.mpq with only 0 b and type .symlink i dont know if this is the problem - replacing with bigger one dont solve issue, checking files doesnt work too.
EDIT: Manage to do screenshot of configuration error 87

There was an issue like this when the game first came out here on GOG, but it was quickly patched with a v2 release because of this, though putting the diabdat.mpq into the dx folder should have fixed this if it was the same issue. In any case, did you get the updated download from GOG?

u should read my post carefuly i mention that i tried to check and update files (i have newest version) and so i tried to replace mpq to dx folder
EDIT: workaround with dx was for win10 machines - i have Win7

В реестре значения заданы корректно?
прикрепил скриншот

It depends on what you mean by update. I don't tend to use GOG Galaxy, instead I just download the installers via the website. The installers and the GOG Galaxy files don't get updated at the same time (though I imagine they both should be up to date by now).

Even though the fix was for Windows 10, all Windows since Vista have UAC and DEP and support for symbolic links, and in theory the same fix could also apply to Windows 7 and 8 which is why I mentioned it.

There may be a registry key present that identifies the CD drive that you need to correct. The value should be a drive letter or path. I can't be sure, though, as I've not yet installed the GOG release of the game.

EDIT: It looks like sifaaa's screenshot may have identified this registry entry.

I checked registry and have same as you, nothing wrong with it.

THE SOLUTION
Looks like editing properties of diablo.exe in main folder to launch with
compatibility mode to XP service pack 2 solved problem, so there is the solution.