Compatible With Windows 10

[Ling Kliment]

Wehave continued our compatible by design approach from Windows 10 to Windows 11, through our multiple efforts across validation, discovery and partner outreach. Based on these efforts, we have a positive signal of the continued compatibility with Windows 11, to the same standard as Windows 10. For cases where changes may cause a compatibility issues, the App Assure program provides the necessary support to ensure that our commercial customers can upgrade safely. In addition to App Assure, Test Base for Microsoft 365 enables our partners to onboard apps to a managed environment and validate.

We recommend that all our partners continue to support the confidence of our shared customers in the new version of Windows by validating that apps are fully functional on Windows 11. The following are a set of guidelines for validation steps specific to the changes made in Windows 11. We will be updating this documentation over time.

There are new minimum hardware requirements for Windows 11. In order to run Windows 11, devices must meet the hardware specifications. Devices that do not meet the hardware requirements cannot be upgraded to Windows 11.

This article has been updated to correct the guidance around the TPM requirements for Windows 11. For more information, see the Windows 11 Specifications. To check the compatibility of your device with Windows 11, get the PC Health Tool from Upgrade to the New Windows 11 OS.

zip -Z sets the compression option. -Z store is the most trivial one, as it doesn't compress at all. This is useful when you're using zip as an alternative for tar, or when troubleshooting. In this case you should try to see if an uncompressed archive is usable from Windows. If that is usable, you know that you'll have to pick a non-default compression option.

In addition to what others suggested, it's important pay Attention to your file and directory names as Windows does not necessarily like Linux file path and names. It sometimes also escapes them differently when zipping. Examples are numerous, but most importantly dot files (. and ..), files with only case differences (name.txt and NAME.txt), absolute file paths (/tmp/file.txt). Some other characters which are allowed in file names on Windows could cause issues when Windows Explorer is used to open files. In my case ':' character was the deal breaker but took a lot of work to find this out.

If this works, you may be better off removing the characters that have been stripped off by -k option from your file/directory names try zipping normally. Note some parameters such as -k have side effects. In this case -k contradicts with -q option (for sym links).

Also -k option may render your file names unreadable. In my case my files were named based on creation time (e.g. 10:55:39.pdf) to facilitate easily locating the required record from archives, but -k option turned it to 105539.pdf which is not easily readable by users. I hence changed the names to 10_55_39.pdf which opens on Windows without using -k option but is still readable.

Had a similar issue recently with files produced from a perl script. Found that native windows zip (tested Windows 7 only) incorrectly handles paths with a leading slash and displays an empty zipfile. Solution was to strip the leading slash before adding files. Perhaps some versions of the linux zip command store file paths with leading slashes.

There is probably a problem in your file transference from Linux to Windows. If youre using FTP, try setting a binary transfer (bin command in Windows, before the transference of your files from Linux to Windows).

last month I bought a new Laptop with better specs than my old laptop. My old laptop works with windows 10, my new laptop with windows 11. On my old laptop lightroom worked very well, without any problems. On my new laptop everything works great, except for lightroom. Lightroom falters and is very slow. Is lightroom classic compatible with windows 11? Or is there a solution for this problem?

Please post your System Information as Lightroom Classic (LrC) reports it. In LrC click on Help, then System Info, then Copy. Paste that information into a reply. Please present all information from first line down to and including Plug-in Info. Info after Plug-in info can be cut out as that is just so much dead space to us non-Techs and it takes up vast amounts of scroll space making the reply less readable and less likely that others will bother with your post.

To get and post better info, in Lightroom, click on Help, click on System Info, click on Copy. Paste that info into a reply (you might want to trim the info down a bit, as most of the info after the plugin info is largely gobblygook to many of use). Photos of a monitor suck, Please actually copy and pastee instead.

Also, Windows 11 as say vs 10 or earlier. Probably many things to turn off, to tweek, etc. You can use Google to search for tips on that. Here is one example with a few that can relate to creative apps like LrC.

You have not shared that system Info yet, so no knowledge on what GPU. Both NVIDIA and AMD have tweeks for performance, at least NVIDIA does. SOme immediately get applied (for NVIDIA in the GeForce Experience, that tweak settings for specific apps) some in deeper in mfg supplied GPU control settings (a bit techie that bit)

You have not mentioned what fails, what is slow, etc. so a bit hard to diagnose. But some LrC settings that can slow things down. These have nothing to do with OS version, but on a new computer, perhaps they got overlooked.

One thing that can get in the way, and a new Windows 11 is going to want to do this. A Microsoft Account, as in logging into that computer using a Microsoft Account instead of a local account. This invokes a very intrusive use of OneDrive. OneDrive can really mess LrC up. First off, accidentally actually placing the catalog on OneDrive, bad, very bad. But more often, concurrent syncing with OneDrive. The latter can/will slow everything down, especially if OneDrive access is having a bad day. Would advise creating a local account, you do not need to login to a computer using a Microsoft account, and if you do want to access OneDrive, that can be done while logged onto a computer with a Local Account. I am not sayeing that the Microsoft account by itshelf is an issue, I am saying that it invoked OneDrive, and that is an issue (if yoyu really want to use a Microsoft account, their is a way to turn any OneDrive association with LrC off)

When I work in the library of lightroom and go from one photo to the other, after a couple of photo's lightroom freezes and one or two seconds later I can continue. It doesn't matter if they have 1:1 previews or not. The same happens when I add keywords to a photo. I can make one or two words at speed, then lightroom freezes and one or two seconds later I can continue to type.

When I go to another application, for instance outlook or chrome, and I want to return to lightroom (the program is open) it takes a second or 10 before lightroom appears and most of the times it doesn't respond immediately.

The last couple of days lightroom isn't responding most of the time at all and I have to wait minutes before I can actually do something in lightroom if I can do something. So the problem seem to becomes worse.

I have still installed lightroom on my old laptop, but I thought I read that it is possible to have this version of lightroom running on 2 computers. On my old laptop lightroom still works just fine.

my pc is running on windows 10 64bit 1909 home single language version. when i am updating the idesign and some of the application then it is showing not compatible. why??. i have latest windows 10 but still why i am not compatible to install and upadte the apps. please suggest me what should i do. i really need to do my assignments.

Thanks for reaching out. Bob is absolutely correct. Windows 10(version 1909) is supported by the latest version of Adobe InDesign. Please find more information on this help article( -guide.html/in/indesign/system-requirements.ug.html).

Thanks for the link, however, the info provided is outdated. Can this please be updated to reflect what is or is not supported? This is one of the first steps my team takes in trying to figure out mass reported issues within the company we support. Currenlty getting complaints with 20H2. That is supported correct?

Now apart from the cheek of Microsoft in throwing a remark like that when not all of us have millions to chuck at a new Pc when we feel like it, I have been told by some Tech guys that the processor Is supported by Windows 10?

It is important to say that one thing is that the graphics controller can support Windows 10 and another thing is that the motherboard manufacturer will release Windows 10 drivers so it is necessary to check with the Computer Manufacture if they will release drivers.

The processor alone does not determine Window 10 compatibility. There are other considerations like the system BIOS, network cards, graphics, and other system components that come into play. For systems running Windows 7* or Windows 8.x*, there is an application available from Microsoft that will tell you if your system is compatible.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

Hey hey @smgoose! I'd be glad to add onto what @Akemi_kun had said. Windows 11 is definitely fully supported for the PC app. You'd just have to be sure you meet our Quest Link requirements for the best performance with the app.

I've formatting d factory reset my quest 2 2 times and used a fresh quest 2 headset as well and airlinknhas not worked on my PC even since windows 11 came out. I can hook it up with a cable but no air like. It's why I won't even consider a meta Facebook quest 3. And I consider myself above avarage as a PC builder and software user. I'm gonna try again in may 2024 but as off right now nothing.

3a8082e126