New
#21
jimbo45
That kills that Idea.. It looks like I am down to trying to fix it by going into the registry. Woe is me.
@jimbo45Office 2007 runs fine in an XP VM too !!! Can't test Office 2010 on this XP VM as office 2010 on my system is X-64 - I don't have Office 2010 X-86 and XP is of course a 32 bit system.
If you can find it Windows XP was available as 64-bit but only the Professional version. I still have a copy amongst one of my software boxes but there weren't many programs or drivers for it 'back then'.
I know I saw it somewhere that the problem can be solved by editing the registry.
If anyone knows where that post is, I sure would appreciate know how to edit the registry and get rid of this BS.
BTW my PC guru says I can install just software in Virtual Box. I just have out how to do that.
I know this is not the solution you wanted but you can avoid all the issues by installing and using Libre Office instead.
First off I found that article for deleting keys from the registry and will be trying that.
The keys are:
HKLM\Software\Microsoft\Office
HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform
NO matter what happens I am not going to use Virtual Box to install another OS on my Windows 10 PC.
I am trying to use Virtual Box forum to find out more about how to use it. That so far is a chore because I sign in to the forum, but dang if I see a way post a question. Maybe some here has a clue how to do that.
Hi there
pose the question on the Virtualisation section on this Forum.
There are some good tutorials as well on VBOX and Virtual machines in general.
Cheers
jimbo
Just a little more info on this issue:
I just got off the phone with Microsoft and at this point there is not a fix with regards to Windows 10 and the 1935 error .
I have been notified that their engineers will have to create a Windows Update with a patch to this issue for Windows 10. How long this will take and where it is in their priority queue, I have no idea.
As far as my end goes I just need to notify the manufacturer of the program we are using of the error (Who just happens to be Microsoft), and they need to provide an updated build for Windows 10.
Knowing how slow Microsoft can be be, this could take years. Windows 11 might be out by then.
I waited a few months after the Technical Preview of Win10 came about and even then the talk was that Win10 would be the last, be continually Upgraded then updated Builds for those Upgrades. The common terms being used are WaaS/Windows as a Service and SaaS/Software as a Service. There are now some third-party softwares being done as a Subscription rather than one-time purchase.
I am just curious if anyone has downloaded and used successfully any of the programs for fixing Error 1935?