Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Everything posted by ivanbuto

  1. Yes, version still works fine, although annoying notifications are shown when clicking on the taskbar icon.
  2. On the other hand, it seems to me that win 7 would be more capable to run modern software if development/support was not cut, and that XP had more limitations in this regard.
  3. Last update for Office 365, version 2002 on Windows 7, is build 12527.22286: https://learn.microsoft.com/en-us/officeupdates/update-history-office-win7 This is how the Account section in Offce applications looks currently (previously, there was a notification that only security updates are installed):
  4. Current version is 69, attempting to install gives an error message: "This version of Windows is not supported"
  5. Google Drive (have version 68 installed) started displaying a nag message that Windows 7 is not supported.
  6. Thanks for the info. Again wondering if there is any way to port these newer versions back to Windows 7, for example if the missing APIs/DLLs were covered by VxKex in the future. Although according to this Microsoft article, "as of January 2022, attempting to do a new installation of Version 2002 will fail." I actually installed version 2002 in February 2022 successfully. I used a custom "Configuration.xml" file to download files for version 16.0.12527.22100 (latest at the time) and then installed locally. Don't know what would happen if one attempted to install in a new setup in the future.
  7. BTW, would there by any way to get this version of Office, which still works for Windows 8.1, to install on Windows 7? I am using the latest supported version 2002.
  8. Obviously, I am aware of all of that. I was asking if anyone else here is able to test, not whether I can share it online... Update: It's again working, confirmed also by a Win8.1 user on MS Community forums.
  9. Does anyone else on this forum use OneDrive for Business accounts on Windows 7? In the last few weeks, I am not able to share files via Windows Explorer. When I right-click a file and select "Share", the share dialog pops up, but the blue circle keeps rotating indefinitely. The same thing happens when I try to share a file from within an Office365 application. I posted about the issue on Microsoft Community forums, but nothing helpful yet. Has anyone experienced this problem? I am using version 22.077.0410.0007 64-bit.
  10. .NET 7, it seems, drops support for Windows 7 or 8.1: https://github.com/dotnet/core/blob/main/release-notes/7.0/supported-os.md The preview builds still supported Windows 7. Don't know if it actually doesn't install and work.
  11. Latest version of Microsoft Teams broken on Windows 7:
  12. OneDrive is now at version 22.131. Any more advice on how to get it to run? Will more versions of VxKex be released? I have not installed it yet. OneDrive 22.077 continues to work OK so far. We'll see what happens in January 2023.
  13. So, latest OneDrive installer (22.089.0426.0003) will not work anymore even with the patch provided by @vxiiduu.
  14. Thanks, this worked... can you explain more? Does this substitute a component of DirectX for something else? However, more errors are on the horizon. I don't know if replacing this file, which does exist in the System32 directory, with a version taken from Windows 10 would work and would be a wise thing to do.
  15. Latest version of MKVToolNix – Matroska tools for Linux/Unix and Windows doesn't launch on Windows 7 anymore. Last version to work thus far is 66.0. Here is the changelog: https://mkvtoolnix.download/doc/NEWS.md The error I get is as follows.
  16. The latest version to run OK seems to be 3.86, later versions give an error that the Process Monitor driver cannot be loaded.
  17. Some Syinternals utilities no longer work on Windows 7. https://docs.microsoft.com/en-us/sysinternals/ I have tested TCPView 4.x x64 and the latest version of Process Monitor, which do not work However, others continue to run fine even with the updated interface, although system requirements are listed as Windows 8.1 or higher. Unfortunately there is a lack of information on the site about which versions are the last good to work on various operating systems, and older versions are not available for download.
  18. So I ended up downloading the missing dll from dll-files.com and placing copies of both 32-bit and 64-bit versions in the respective Windows system directories. Managed to install Vidcoder 7 successfully! (Whether there might be issues with the software when actually using it is to be determined).
  19. Vidcoder v7 now refuses to install on Windows 7. https://github.com/RandomEngy/VidCoder/releases/tag/v7.12 It uses .NET 6.0. It also uses HandBrake 1.5, which requires Windows 10: https://handbrake.fr/docs/en/1.5.0/technical/system-requirements.html The following error appears upon launching the installer: I posted about the issue here: https://github.com/RandomEngy/VidCoder/discussions/974 It seems this issue occurs with other software as well, and perhaps can be fixed? https://github.com/dotnet/core/issues/6976 https://github.com/NickeManarin/ScreenToGif/issues/1077
  20. Also, I don't want to flood this thread with OneDrive discussion, so perhaps we can make a separate topic for this.
  21. Wow, thanks for your efforts! I'll be glad to understand better how this works, I assume OneDriveSetup.exe uses the "local" kernel32.dll. I've been unsuccessful following the instructions thus far. Get the following error upon launching OneDriveSetup.exe.
  22. Thanks a lot! Seems that the current version 22.002.0103.0004 does not contain the mentioned hex strings, though. Could you take a look at it? How did you determine those were the ones to change in the previous version? The reason for me is simple - we use OneDrive quite a lot at work. While I have a Win10 work laptop, I also keep my core files on my home PC machine, which has relatively recent hardware (Intel Z390 chipset) and on which I run Windows 7. The app has worked with no problems thus far. It's a shameful behavior by MS to deliberately break products in this manner. Then again, they did something similar together with Intel where they decided to not allow people to install Windows 7 on anything higher than Skylake.

  • Create New...