Just bought Fallout 4 and when firing it up got two alerts:

- Fallout4.exe doesn't have a valid digital signature
- Fallout4.exe tried to access protected Windows core file

Whats up GoG! I removed the game and will be getting back to you for a refund. Get your act together, and till then I get my games at Steam

Hmm... Strange. It works fine here. Did you by any chance installed the game in the Windows directory or one of the two Program Files directory's? If so - Those directory's are heavenly protected by Microsoft Windows. You better install (any) game in something like C:\Games or C:\GOG Games (or even on another drive).

If above is not the case, did you by any chance has the Steam version installed prior the GOG version? If so, especially if modded, remove all traces from the Steam version. Make a backup from your save files (C:\Users\"username"\Documents\My Games\Fallout4), and delete the Fallout4 directory. Especially if you had modded the Steam version, there will be .ini files that give big problems. You have to start clean with everything (that includes removing all mods in Mod Organizer 2 or Vortex).

This is not a "GOG-Issue". JClosed is right with everything he wrote. Don't install games (especially modded games) into the "Program Files-Folder" or into the root of your "System-Drive" (normally C:). These are protected folders.

I looked into it, and the game was installed in E:\GOG Galaxy\Games\Fallout 4 GOTY, far away from any system or Windows folder. I reinstalled it into the same folder, just to be sure, and the same thing happened. The file accessed is C:\Windows\INF\keyboard.PNF

You also read my other advises?

I mean - Did you had any previous (modded or not) Steam version of this game installed?

Secondly - How did you install? Did you use Galaxy or off-line installers. If the latter is the case, there could be a corrupted file in between the install files. Try installing and use the "Check File Integrity" feature in the installer to see if the files are corrupted some way.

Otherwise there could be something wrong with your virus scanner (probably Norton, because that's hot garbage), or you have a faulty "something" driver. This is a very strange error, and absolutely not something I see often.

Accessing the keyboard.pnf-file is normal. A PNF-File contains a configuration file managed by the system. The PNF-File is normally removed after the INF file is closed.

Like JClosed mentioned: Maybe it's your security-software. I installed it without any issues and I'm a IT-Professional, I work under Linux und play under Windows-VMs with high security.