Discussion in 'Microsoft Office' started by l2p2c2, Aug 17, 2010.
You need to login to view this posts content.
@abbodi1406 @Tito App-V is not something that I am overly familiar and not something that I had specifically enabled.
However, the only thing that comes to mind is Office 2016 C2R. I had been playing with that recently off and on and eventually went back to Office Starter 2010.
Would Office 2016 C2R install process have enabled App-V Client? Is this something that can be left enabled after uninstalling Office 2016C2R?
I had always removed Office 2016 C2R using the Microsoft tool which uninstalls it (instead of via Control Panel). Thank you both for your time.
I'm not familiar with either
i just wanted to refer about its existence in Windows 10 (1703 & 1709)
and according to product policies, it's allowed for Enterprise/Education only
Just in case anyone else runs into this issue with Office Starter 2010 not working on Windows 10 (more recent versions).
The root of this issue ended up being the failure of the App-V version (4.6.x) which is installed/used by Office Starter 2010 (and likely other 2010 Click-to-Run versions). App-V was failing due to kernel-mode driver digital signature being denied. There are a handful of App-V drivers here (C:\Program Files (x86)\Microsoft Application Virtualization Client\drivers) which are also located in the System32\drivers directory.
The drivers only have a SHA1 signature and are signed back in late 2014 and therefore are missing SHA256 and Microsoft Windows digital signature required by modern Windows 10 versions, likely Anniversary Update, Creators Update, and Fall Creators Update. Although I had no issues running Office Starter 2010 on Anniversary Update and Creators Update. This issue only started for me on Fall Creators Update.
Anyway, to fix this issue, I had to add the UpgradedSystem/BootUpgradedSystem dword entries in registry to make the system think that it was upgraded and therefore not enforce the Microsoft Windows cross-signed digital signatures for kernel-mode drivers.
From a security perspective, this is a bad idea to disable the Microsoft Windows cross-signed digital signature requirement. The better idea from a security perspective would be to run Office 2016 and take advantage of more modern process mitigations such as Control Flow Guard and even also opt-in for the Disable Child Process mitigation to prevent Office apps from spawning child processes.
Anyone with the latest SetupConsumerC2ROLW sk-sk (slovak)? All links are dead. Thanks a lot in advance!
3 sec to find a mirror
please post, i cant find it
Does not work on Windows 10 ver 1709 even after adding these settings to the registry. "This app can't run on this PC"
Update: works after some windows updates installed.
works perfect in windows 7 !
thank for this tool, work fine on w10x64 ver 1709, Q partition hide well too, thx all
Does anyone have the latest SetupConsumerC2ROLW for hu-hu?
which is the latest version?
For what it's worth, Microsoft seems to have killed off 2010 ClickToRun versions (including Starter) on Windows 10 1803 starting with KB4103721 (OS Build 17134.48). I don't think that it was intentional though because they would have killed it off with the initial 1803 build if that was the case. But so far they have not fixed it yet with KB4100403 (OS Build 17134.81), KB4338548 (OS Build 17134.83), or KB4284835 (OS Build 17134.112).
The error has to do with the startup of the Service for Client Virtualization Handler. It reminded me similarly of the recent Quicken/QuickBooks issue that was patched which was a Service start issue also and was patched by Microsoft in KB4100403 (OS Build 17134.81) if I remember correctly. So I was hoping it might also fix the Service start issue with Office 2010 Starter C2R but unfortunately it did not fix the problem, nor did any subsequent 1803 updates.
I've tried several clean installs (offline; with individual cumulative updates) as well and it always gets killed at the same update. I've spent too many hours and days trying to troubleshoot this one. So I ended up having to move on to Office 2019 Preview builds. I was always a big fan of Starter since it covered what I needed and was quite minimalistic.
Note: This already had required the "upgrade-install" regkey tweak which bypassed the SecureBoot Microsoft Windows co-sign requirement for the kernel-mode drivers of the Client Virtualization Handler which is required for the ClickToRun versions. Unfortunately this method also degraded security for the only purpose of running Office 2010 Starter.
Thank you for sharing your success with this, I am happy that you have got it working.
I just tried another clean install of 1803 again and Starter has failed again for me.
I will try to install again (clean) and try installing the updates manually as you had mentioned.
BTW, is your 1803 install 64-bit?
Yes, I have 1803 x64 Pro English US,
but another small note. The version of Microsoft Office, that is installed, is a 32-bit, regardless of your system and installer, so you also need all KB 32-bit versions only. I forgot say about it before. If You will try to install 64-bit updates, these will not install.
This happens even if You will install paid Microsoft Office 2010 Pro for example.
I have tried, in Windows 7-8.1 installs 64-bit version, but in Windows 10 only x86, ie 32-bit version. That's it.
This is a personal experience. (I have five package of retail versions, part is not even opened yet.)
a working version would be enough for me