Latest WIP error

[Piotr]

John

Can you bypass it i your msi?

[John_Brock]

I’m hoping that when @brian tunes up the V6 MSI installer, this problem will go away.

[Piotr]

I keep my fingers crossed. I don’t want to change my machines yet or switch to Win 10.

[brian (Brian Gillespie)]

@John_Brock

It appears this may be a problem Microsoft is working on

I don’t think so. That bug report was specific to Windows Server 2012, and Piotr is running Windows 7.

@John_Brock

That log doesn’t follow the same “rules” as MSI error logs.

Nope, but you’ll get used to these logs soon enough - they are the ones generated by the bootstrapper engine that we’ll be using shortly for Rhino WIP. The top says “Burn v3.7.3813.0” - Burn is the bootstrapper/chainer we’ll be using.

@John_Brock

I’m hoping that when @brian tunes up the V6 MSI installer, this problem will go away.

I doubt it. If the standalone installer from MS doesn’t work, it’s not going to work when embedded in our installer, either.

@Piotr

Can you bypass it i your msi?

Well, clearly we already do! THat’s why you don’t have the correct files on your computer, and yet you are still able to try to start Rhino. But once I fix the bug, the installer will fail for you until this redistributable package is properly installed.

I recommend you contact Microsoft Support for help getting that redistributable package installed - there’s nothing we can do to help you until your computer is updated with it.

[John_Brock]

@brian

I don’t think so. That bug report was specific to Windows Server 2012, and Piotr is running Windows 7.

@brian
I read through the message replies.
There are several people reporting the identical symptoms in Windows 7.
That’s why I posted the link.