Our NTFS tools simply can't handle the data we're getting in. We didn't see this in our own 1703 testing, so I guess the updates hadn't happened before our testing concluded. Some recent Windows 10 update from Microsoft (which definitely applies to 1703 but might also be in 1607) is introducing new filesystem stuff which they have not used before. I've been having some minor issues in my VMWare environment this week, but the first failure was this weekend before those issues began.Īnyone else seeing any issues like this? I tried searching the docs and found a reference to the "A function was called with an invalid parameter" error in a 2.10 error list, but the page it links to on is no longer available.Īm I on the wrong track upgrading my existing OS layer to 1703? I thought it was possible to do Windows 10 Feature Upgrades in an existing OS layer and I really don't want to have to recreate all my app layers.
I've tried rebooting the ELM but it keeps failing with the same message. Please address this issue and retry: A function was called with an invalid parameter." But it at least doesn't delete the layer version. The second time it's just been giving me this error "An error occurred while finalizing version '' of Layer ''. It failed with the error "vCenter returned an error: InvalidDeviceSpec" and it deleted my layer version, so I had to do the whole process over again. I performed the feature upgrade to 1703 using Windows Update and then tried to finalize.
Last week when App Layering 4.7 came out I upgraded to that and then added a new version to my existing WindOS layer.
0 kommentar(er)
