Importing Flash packages for multiple Windows 10 releases

Occasional Visitor

Hi - I'm wondering if anyone else has seen this behaviour and, if so, how they've gotten around it.

 

I have Deployment Workbench organised into folders representing different releases of our image - our current image is based on 1709 and I'm starting work on a new image based on 1809, so I now have 2 sets of folders within each category - one for the 1709 image and one for the 1809 image.

 

I've successfully imported the Jan '19 security package for Win10 1809, but when I try and import the Jan '19 Flash security package for Win10 1809 the import wizard gives me the following:

Not copying existing package C:\Users\probinson\AppData\Local\Temp\MSUexpand\Windows10.0-KB4480979-x64.cab

Copying existing item Package_for_KB4480979 neutral amd64 10.0.1.0 from DS006:\Packages\1709 to DS006:\Packages\1809.

This is, I assume, because I've previously imported the 1709 specific Jan '19 Flash package.

If I try and build my 1809 image with the 1709 Flash package, the build understandably fails with a DISM error.

 

So my question is this - how do I import and manage the monthly Flash packages for both my current build and new build within the same Deployment Share?

 

Looking forward to hearing from you - and if I need to provide more detail just let me know!

 

0 Replies