wimcapture + wimappy breaks office?
Posted: Sun Jan 30, 2022 1:50 am
Hi,
It seems that wimcapture fails to capture some significant data or metadata for (at least) a particular DLL needed for a working office 2021 installation. I tested in a virtual machine running Windows 10 21H2 + Office 2021 but it seems to also break Office 2019 in the same manner. This DLL is specific to the cloud installation (used for Office 365 also), but I do not have a conventional/offiline license to test with the non-cloud edition. In case it matters, it is an x64 edition of office.
I have a snapshot before the capture of everything working fine, but simply wimcapture the volume (offline), format the partition, and wimapply the very same image back seems to break office. I am happy to help test/debug stuff since I have VM snapshots in the pre-capture and post-apply states as well as the image itself.
Edit: Just to be clear, the DLL is present and SHA256 identical to the base image, but it is not recognised by office for whatever reason... presumably some hidden NTFS stream or permission?
It seems that wimcapture fails to capture some significant data or metadata for (at least) a particular DLL needed for a working office 2021 installation. I tested in a virtual machine running Windows 10 21H2 + Office 2021 but it seems to also break Office 2019 in the same manner. This DLL is specific to the cloud installation (used for Office 365 also), but I do not have a conventional/offiline license to test with the non-cloud edition. In case it matters, it is an x64 edition of office.
I have a snapshot before the capture of everything working fine, but simply wimcapture the volume (offline), format the partition, and wimapply the very same image back seems to break office. I am happy to help test/debug stuff since I have VM snapshots in the pre-capture and post-apply states as well as the image itself.
Edit: Just to be clear, the DLL is present and SHA256 identical to the base image, but it is not recognised by office for whatever reason... presumably some hidden NTFS stream or permission?