Puppet on Windows has been upgraded from 2.7.22 to 3.5.1 on Windows7. When puppet apply was executed it looked like puppet was stuck. A retry demonstrated the same behavior and the run finished after minutes, while puppet indicated that the run took 0.17 seconds. Neither a bug regarding slow performance of Puppet on Windows nor identical questions including time analysis were found. One related question was found.


An identical puppet apply (puppet apply "C:\temp\puppettest\site.pp") was executed using several Puppet on Windows versions. The results are as follows:

  • 2.7.23: X < 10s
  • 3.0.2: X < 15s
  • 3.1.1: X < 15s
  • 3.2.4: X < 15s
  • 3.3.2: X > 420s
  • 3.4.3: X > 420s
  • 3.5.1: X > 420s


Puppet Apply on Windows more than 28 times (420/15) slower since version 3.3


How to solve this issue?

  • Does --debug provide any info on what it's doing during that time? – Shane Madden Apr 30 '14 at 19:10
  • puppet apply --debug "C:\temp\puppettest\site.pp" does not show any debug information. The cursor flashes until the puppet run has been finished. – 030 Apr 30 '14 at 19:16
  • How about with --verbose as well? – Shane Madden Apr 30 '14 at 19:17
  • When the puppet run finished it showed more information thanks to the --debug option. I will add --verbose as well and post the output. – 030 Apr 30 '14 at 19:18
  • 2
    Would it be possible to get some information on the network adapters you disabled? In PowerShell, you can use the Get-NetAdapter command to retrieve basic info. If you'd like to file a ticket at tickets.puppetlabs.com, then we can track this issue. Thanks! – Ethan J. Brown May 1 '14 at 21:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.