Error 1935 Any Fix Soon

Page 2 of 4 FirstFirst 1234 LastLast
  1. cereberus's Avatar
    Posts : 12,014
    Windows10
       #11

    huffman said:
    When using Windows 7, Office 2003 works great. With Windows 10 it is being a PITA.
    Do you seriously expect Windows to remain compatible with old versions of any software for ever?

    If you need to run old software, install Win7 in a virtual machine.
      My Computer

  2. jimbo45's Avatar
    Posts : 10,489
    Windows / Linux : Arch Linux
       #12

    Hi there

    Agree absolutely

    Virtual machines run easily these days on even quite modest hardware - if you don't have W10 PRO run on VBOX / VMWare player - both free. With W10 PRO enable HYPER-V.

    For the VM if you basically just want Office 2003 you can simply use a minimal W7 install -- just install office - and use say W7 X86 (32 bit version). Same key should work as per original installation - if you need to activate just do it by phone and say moved to new computer -- Ms activation for this stuff is quite painless and 99.99% of the time it should work.

    Cheers
    jimbo
      My Computer


  3. Posts : 368
    windows 7
    Thread Starter
       #13

    YEP it is definitely and OLDIE.... but a goodie.
    It is brought and paid for it the best part. I will NOT buy another version.

    I still believe Microsoft can be really stupid at times and when let this error to continue, it just confirms my opinion.

    I am still working on the problem.

    In a couple hours I should be able to chat with Microsoft support and maybe get the answer to the problem.
      My Computer

  4. jimbo45's Avatar
    Posts : 10,489
    Windows / Linux : Arch Linux
       #14

    Hi there

    @huffman

    what's not to like about the VM solution.

    Here's a VM running XP and Office 2007 !! The W10 Host would hardly know it's running as it uses almost zero resources.

    Error 1935 Any Fix Soon-menu.jpg

    You can't expect companies to support software / hardware for ever

    For example in the old part of what was DDR / GDR - East Germany - would you expect mainstream garages still to support and repair the old Trabant (ran on lawn motor 2 stroke fuel and pollution would outlaw this vehicle on almost any country on the planet today !!!) .

    And to cap it all those poor citizens had to put their name down when a child was born so they could actually get one of those "Vehicles" after an 18 year old wait when the kid had grown up. !!!!

    Error 1935 Any Fix Soon-trabant.png

    Give me a BMW ("Beamer" ) any day !!!!

    Cheers
    jimbo
      My Computer


  5. Posts : 368
    windows 7
    Thread Starter
       #15

    Actually yes I can expect MS to support the product they sold me even if it was 15 years ago. I am not the only one experiencing this problem Office 2007, 2010 and I expect others are seeing the same thing I am seeing.

    I will check the VM thing out. I sure as heck not paying for another Office.
      My Computer


  6. Posts : 368
    windows 7
    Thread Starter
       #16

    One Pissed Windows 10 user here. I tried to install Open Office and guess what. Same dang Error 1935. WTF.

    Now if I use Virtual Machine can I install Office 2003 in the Virtual Box?

    I was checking VM and it said VM expires after 90 days. Is this true? Really is of little or no value if that is true.
      My Computer

  7. jimbo45's Avatar
    Posts : 10,489
    Windows / Linux : Arch Linux
       #17

    Hi there

    @huffman

    can't understand that -- VBOX is FREE, as is VMWare player. Check if you didn't use commercial rather than home versions of these things. Home versions have free perpetual licenses.

    You need also to have a valid version of Windows for your Guest OS (the VM) and the relevant key for your version of office.

    What is giving you the 30 day expiry notice - remember installing software on the guest system is just the same as installing it on a physical machine -- activations and serial numbers must be entered / done in the usual way.

    BTW Office 2010 works 100% perfectly on W10 even the latest skip ahead build and is in support until late 2020 so "plenty of life in the old dog yet".

    However as others have said you can't expect companies to support old software and hardware indefinitely --

    you can though run legacy hardware and software on new equipment using Virtual machines -- a lot of people do this very successfully.

    "Can you repair my old 160Kb 8 inch IBM floppy disk drive please" !!!!!

    Cheers
    jimbo
      My Computer

  8. jimbo45's Avatar
    Posts : 10,489
    Windows / Linux : Arch Linux
       #18

    Hi there
    @huffman

    Office 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.

    Error 1935 Any Fix Soon-o2007.png

    Cheers
    jimbo
      My Computer


  9. Posts : 368
    windows 7
    Thread Starter
       #19

    Tell me if this is correct:

    If I install VM Box, I can then install software such as Office 2003 without getting Error 1935?
      My Computer

  10. jimbo45's Avatar
    Posts : 10,489
    Windows / Linux : Arch Linux
       #20

    Hi there
    after installing VBOX you have to install a Guest OS (i.e a Windows Virtual machine).

    To install simply run Virtual Machine Wizard which will prompt you through the steps, then install VBOX additions on the Guest OS (fixes display etc for modern monitors etc) and then install your Office 2003 on the Guest OS.

    The GUEST OS should be Win 7 or earlier for Office 2003. You'll need serial numbers for both Win 7 and the office 2003 product.

    Cheers
    jimbo
      My Computer


 
Page 2 of 4 FirstFirst 1234 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 05:23.
Find Us




Windows 10 Forums