On Friday, February 3, 2017 at 1:48:28 PM UTC-5, Christian Brabandt wrote: > On Fr, 03 Feb 2017, Blay263 wrote: > > > On Friday, February 3, 2017 at 2:27:02 AM UTC-5, Christian Brabandt > > wrote: > > > On Do, 02 Feb 2017, Blay263 wrote: > > > > > > > Windows 10 blocks you from running the actual .exe files.I just > > > > found it odd that the .exe files from vim.org install without any > > > > problems but the nightly builds are untrusted and thus blocked. > > > > Both the standalone and the .exe in the zip folders. > > > > > > I don't know of any way to fix this. If there is and we can actually > > > do anything about it, I love to hear. > > > > The only thing that comes to mind is that do the executables from the > > main website have a trusted digital signature that can be transferred > > to the nightly builds ?? > > Don't you have to type a password for signing? I admit I have never > looked into how to sign a binary and I don't know if Bram did that with > the official builds > > Best, > Christian > > -- > In den meisten Fällen ist Glück kein Geschenkt, sordern ein Darlehen. > -- Albrecht Goes
ok turns out it was a bug Windows 10 November update (version 1511).An update of my OS solved this issue. Thanks for your help -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
