Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations

    0.00 USD 

WinFX last won the day on December 3 2019

WinFX had the most liked content!


About WinFX

  • Birthday September 18

Contact Methods

  • MSN

Profile Information

  • OS
    Server 2012 R2

Recent Profile Visitors

6,863 profile views

WinFX's Achievements



  1. What is the command to use Chromium 111 on Vista with the latest extended kernel of March 9, 2023?
  2. Show me your winword.exe on dependency walker x64 and show full path
  3. Guide available to install Office 2013 on Vista!
  4. How to install Office 2013 on Vista 1- Have a copy of Office 2013 64-bit handy (The latest extended kernel is needed, x86 is useless) 2- Copy to the desktop in a new folder the root of your copy of Office 2013 3- Copy the ProPlus.WW.en-US folder to the desktop (the name may vary due to the language/edition of the copy), this is important since the Office installer detects the edited files and the installer of this folder needs to be edited. 4- In the folder copied to the desktop open ProPlus.WW.msi with Orca, go to InstallExecuteSequence and remove AbortMsi (it blocks the installation outside of setup.exe that verifies the files), then in Components change all Conditional VersionNT >= 601 by VersionNT >= 600. 5- Replace gdiplus.dll with the one from Windows 7, this is the path in the system: C:\Windows\winsxs\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.19749_none_56a723b1b598503f\gdiplus.dll 6- In group policies of the local machine, it prohibits rollback (very important) 7- Create an osver.ini file with the following settings (required at all times when installing Office 2013): [global] MinorVersion=1 BuildNumber=7600 8- Open ProPlus.WW.msi and after installation the Office 2013 suite should appear in the start menu, but it is not enough! 9- Go back to group policies and disable rollback, but keep osver.ini 10- In the root folder of Office 2013 the only change we will make is to delete the update or updates folder, they cause bugs when installed 11- Open the setup.exe of the normal Office 2013 installer and customize it to your liking (it should install successfully, if an error appears, reboot the system) 12- Open Word 2013 (it can be any program in the suite except Visio, Lync, InfoPath or Outlook) to configure Office 2013 13- The programs of the Office 2013 suite will need to be detected at all times as Windows 7 or an annoying Windows Installer dialog will appear configuring each time the program starts: [C:\Program Files\Microsoft Office\Office15\EXCEL.EXE] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\MSACCESS.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\MSPUB.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\ONENOTE.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\OUTLOOK.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\POWERPNT.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\WINWORD.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 14- ¡Enjoy Office 2013! SOMEONE BUGS 1- A large part of the office suite worked without problems, but there are programs that have some problem to solve: Outlook: won't start due to missing dependency on advapi32.dll (in future extended kernel updates this may be fixed) Lync: Stop responding... on welcome screen Infopath: Won't even open Visio: When creating a new drawing stops responding 2- It is impossible to activate it (at least there is no time bomb) 3- Can't login (maybe because of TLS) CONCLUSION We have partly killed the obsolescence imposed by M$ in Vista, which only received two versions of Office. Almost the entire suite works perfectly under Vista, except for Lync or InfoPath that I don't find useful, Outlook and the lack of dependencies in advapi32.dll. In the usual programs like Word, Excel or Powerpoint I can do anything without problems as if I were in Windows 7 or 8.
  5. News about Office 2013 on Windows Vista The full suite of Office 2013 Pro Plus installed on Windows Vista. A dream come true, maybe... I have managed to install Office 2013 on Vista and I have the method so that it can be installed without errors (it works with any program in the suite, except for Visio, which appears as an unconfigured application when trying to start it). It remains to see a problem about the license not being found, the same problem occurs in Windows 2000 when installing Office 2007 with a very similar manual, which is solved by importing a Windows XP key with the same installed copy of Office 2007. I will have to try if it works by installing my copy of Office 2013 on Windows 7 and importing that key into Vista. But then there are programs from the suite that are unfortunately unusable (at least for now). Some extra programs like "Send to OneNote" seem to work correctly. Here is an image of "Send to OneNote 2013" working correctly. At the moment I do not want to share the method to install Office 2013, at least until I can solve the license problem. When much of the suite works, I'll share a method in a separate topic and just dedicated to installing Office 2013 (and maybe newer versions) on Windows Vista, to make it easier to find.
  6. I'm working on getting Office 2013 to work on Vista, I tried an old method to install Office 2007 on Windows 2000. I had to replace the gdiplus.dll that comes with Vista, with the one that comes with Windows 7. But I get a license error, I have only tried project, I have not tried visio or the complete suite (Word, Excel, etc). Then the office tools, such as the language configurator seem to work without any problem.
  7. new version of vmware is out 17.0.0 Does it work with Windows 7? Or is it no longer possible?
  8. It would be very useful, especially Windows 8.0 and LTSB 2015 that have many artificial limitations that Windows 7, 8.1 and LTSB 2016 do not have.
  9. Windows 7 works perfectly on my alder lake, except for one exception, the ethernet. There is a leaked driver (https://mega.nz/file/P2wh2a4D#MaXWUXyunUxS6UiHuM4xvdX-65Dilga4KLEd1ztMfdI) but it is for i225-V, does anyone know an i219-V driver for Windows 7? This is my hardware ID: PCI\VEN_8086&DEV_1A1D&SUBSYS_86721043&REV_11
  10. Windows Update from v3 to v6, even on Windows 11 it uses: http://download.windowsupdate.com to download updates, the IE5.x installer still exists there, we are currently working on a project to revive Windows Update v4 with SUS and no link has fallen. The download center is different, since there are even Windows 7 updates, which were removed but are still in the catalog.
  11. Windows Update v6 works from March 2022 on all systems thanks to ProxHTTPSProxy 1.3, to fix the redirect problem just add g_sconsumersite. Windows Update v5 works from June 2022, but until October 2022 only critical updates could be installed, since then optional Software/Hardware updates could be installed. Windows Update v4 has recently returned to work thanks to SUS but only in Automatic Updates in Windows 2000 SP2+. And Windows Update v3 works since August 2022, the site was revived in any way, but it only works in the most widely spoken languages, and the inventory system is old, October 2000.

  • Create New...