Technically no. Ngen executequeueditems is not the same as Ngen update, hence the different command . Ngen executequeueditems does just that, it only processes items already in the queue for processing. This occurs in the background, it Ngen update processes all targets. The queued items are done by Windows anyway and done fairly quickly after an update. The update command goes much further, it recreates images that have become invalidated.