sleerfnivek
Participant
sleerfnivek
Participant
Activity
14 hours ago
Just wondering if you ever resolved this. My system isn't as good as yours but it's only a 2-year-old machine with 16 gig And I only had problems after upgrading to Windows 11 in mid-December. Prior to that I have been running 26.2 both beta and release versions with no issues. Now I have a problem with it shutting down on file>open that began in December when I decided give Windows 11 another go and decided to do it as a clean install. Right out of the gate I had this problem. It functions otherwise normally. I can right click files and either open with or send to Photoshop fine And I can open them through bridge. The reason I'm asking you is because after frustrating hours of working with support remotely logged in still not finding the issue, I began installing versions backwards one at a time to identify where the failure is happening and it happens between versions 25.9 and 25.11. This was in June of last year. Compatibility checker shows that it's compatible And I found that if I launch it holding shift to prevent plugins from loading, it operates fine. What baffles me is that I don't have any plugins installed. Trying to identify what else changed between those two versions that's causing this problem that was not causing the same problem on Windows 10....
... View more
‎Feb 28, 2025
12:38 PM
Still getting nowhere with this and getting quite frustrated. I just did moved over to the Windows Insider edition because there's a fix there for a slow right-click problem in Explorer. The update took about 2 hours so I'm assuming it was a major revision. Booted back up and still have the same problem. As mentioned before, I didn't have this problem with 26.2 on Win10 in mid December. But After a clean install of Win11 in mid December I've had this problem and the problem is there all the way back to 25.11. v25.9.1 does NOT crash on FILE>Open. 25.11 and every version after does. So what changed between 25.9.1 and 25.11?
... View more
‎Feb 25, 2025
12:05 PM
To summarize and hopefully get some attention, this appears to be a problem for a number of people that have likely been misled to think that the problem is their machines...Specifically Lenovo systems with intel shared graphics running Win11. My machine specs show intel integrated graphics with 128MB dedicated and 8GB shared memory, 16GB total memory. The crash report shows 1GB graphics memory which is not what the specs show. It IS what msinfo32 shows but there's a known issue with it reading over 1GB. DXDiag.exe shows 8179MB display memory. It's only two years old and had no problem running PS 26.2 and Beta 26.3 in December under Win10. I clean installed Win11 in mid December as well as Photoshop 26.2 and Beta 26.3 as was running on my Win10 system. Since then, I get an error on FILE>OPEN for any version after 25.9.1. I've installed each version from the available 23.1 up to the current version, one at a time, testing this with each. All versions up to 25.9.1 operate as expected. 25.11 and all versions since have this problem. The problem is ONLY experienced in Photoshop, not Illustrator, Bridge, Acrobat, etc. It runs perfectly fine otherwise. I can open files from my Adobe cloud folders. I can right-click files and "Open With" Photoshop 26.3 Release and Beta 26.5 20250223.m.2987 and everything works perfectly other than FILE>OPEN. No hardware requirement changes happened between 25.9.1 and 25.11 but this is where the problem occurs. The Graphics tool is all green with "Your graphics processor is compatible". So the question is.... what changed between 25.9.1 and 25.11? Why does the crash report show 1GB of graphics memory if my specs are 128MB dedicated/8GB shared? If it were really an actual graphics or memory problem due to it not reading intel shared video memory correctly (8179MB according to DxDiag.exe) why does the problem only occur on FILE>Open but runs perfectly fine otherwise, including opening from Adobe Cloud? Since I was running 26.2 on this very machine under Win10 and now can't run past 25.9.1, I feel I can safely say that the cause of this problem isn't my machine and isn't the specs. Something changed in 25.11 and every version since that it likely affects many users with Lenovo Thinkpads with intel shared graphics, running Win11. Here are the specs from the PS output if anyone is interested: Adobe Photoshop Version: 26.3.0 20250122.r.156 bfca642 x64 Number of Launches: 5 Operating System: Windows 11 64-bit Version: 11 or greater 10.0.26100.3194 System architecture: Intel CPU Family:6, Model:14, Stepping:12, AVX2, HyperThreading Physical processor count: 4 Logical processor count: 8 Processor speed: 2112 MHz Built-in memory: 16103 MB Free memory: 10312 MB Memory available to Photoshop: 11858 MB Memory used by Photoshop: 70 % Crash Handler: Adobe DCX Version: 7.24.14 SAM SDK Version: 9.1.0.2-fio ACP.local Status: - SDK Version: 4.0.0.6 - Core Sync Status: Reachable and compatible - Core Sync Running: 7.4.0.31 - Min Core Sync Required: 4.3.66.28 Live Edit Client SDK Version: 4.0.6 Adobe Firefly: Please use any generative AI feature to view the latest version. OpenColorIO version: 2.4.0 C2PA library version: adobe_c2pa/0.12.2 c2pa-rs/0.32.5 NGL Version: 1.40.0.8 Chalkboard: Disabled. Chalkboard Doc Create: Disabled. D3D12Warp renderer: Disabled. Precise Color Management for HDR Display: Disabled. Alias Layers: Disabled. Highbeam: Disabled. Image tile size: 1024K Image cache levels: 4 Font Preview: Medium HarfBuzz Version: 7.3.0 TextEngine: Unified Text Engine ======= GPU Native API stable: True OpenCL API stable: True GPUDeny: 0 GPUForce: 0 useGPU: 1 useOpenCL: 1 isGPUCapable: 1 isGPUAllowed: 1 GPUName: Intel(R) UHD Graphics GPUVendor: INTEL Intel(R) UHD Graphics UNKNOWN, INTEL IsNativeGPUCapable: 1 IsOpenCLGPUCapable: 1 HasSufficientRAM: 1 GPU accessible RAM: 8,570 MB Required GPU accessible RAM: 1,500 MB UseGraphicsProcessorChecked: 1 UseOpenCLChecked: 1 Windows remote desktop: 0 Windows available feature level: 12.1 Windows required feature level: 12.0 Windows has required feature level: 1 Display: 1 Display Bounds: (0, 0) -> (1920, 1080) Display scale: 1.25 Main Display Display Type: SDR Display Profile: sRGB IEC61966-2.1 ------- Sniffer output [0 ms] Launch GPUSnifferThread [1 ms] Start RunAllAPIs [1 ms] C:\Program Files\Adobe\Adobe Photoshop 2025\sniffer.exe -baseTimeMS=9842149 -comment=Photoshop Version: Adobe Photoshop 26.3.0 20250122.r.156 bfca642 x64 [1 ms] Start GetSnifferResult [1249 ms] Start sniffer 2025-02-25 13:46:13 # Photoshop Version: Adobe Photoshop 26.3.0 20250122.r.156 bfca642 x64 C:\Program Files\Adobe\Adobe Photoshop 2025\sniffer.exe -baseTimeMS=9842149 -comment=Photoshop Version: Adobe Photoshop 26.3.0 20250122.r.156 bfca642 x64 {191 ms} Start platform native # displays: 1 Display 0 Display: \\.\DISPLAY1 Main: TRUE Built in: FALSE Stereo: FALSE Bounds: (0, 0) -> (1,920, 1,080) Dimensions: (1,920 1,080) Display scale: 1.25 Physical size: (0 0) Pixel size: (0 0) Dynamic range: (0 1) Attached Device: (DeviceID name=Intel(R) UHD Graphics index=0) # devices: 1 Device 0 Name: Intel(R) UHD Graphics Preferred: TRUE Power Envelope: UNKNOWN Attachment: UNKNOWN # attached displays: 1 \\.\DISPLAY1 GPU accessible RAM: 8,570 MB VRAM: 128 MB Dedicated System RAM: 0 MB Shared System RAM: 8,442 MB API version: 12.1 (12.1) Device version: 12.0 (12.0) Vendor name: INTEL Driver date: 2024-08-13 000000.000000-000 Driver age: 6 months Driver version: 31.0.101.2130 Supports UMA: SUPPORTED D3D-ID: 39745 End platform native {331 ms} {331 ms} Start platform OpenCL # displays: 0 # devices: 1 Device 0 Name: Intel(R) UHD Graphics Preferred: TRUE Power Envelope: INTEGRATED Attachment: UNKNOWN # attached displays: 0 GPU accessible RAM: 6,754 MB VRAM: 6,754 MB Dedicated System RAM: 0 MB Shared System RAM: 0 MB API version: 3.0 (OpenCL 3.0 ) Device version: 3.0 (OpenCL 3.0 NEO ) Vendor name: INTEL Driver date: UNKNOWN Driver age: UNKNOWN Driver version: UNKNOWN Bandwidth: 19 GB / s Compute score: 182.645 Device name string: Intel(R) UHD Graphics Device vendor string: Intel(R) Corporation Platform name string: Intel(R) OpenCL HD Graphics Platform vendor string: Intel(R) Corporation End platform OpenCL {1216 ms} Exit code kExitNormal End sniffer 2025-02-25 13:46:14 [kStatusNormal, kExitNormal] [1250 ms] Finish RunAllAPIs [1257 ms] Finish GetSnifferResult
... View more
‎Feb 24, 2025
12:30 PM
Well, today, since I primarily use the beta, I uninstalled the regular release version. I did a complete uninstall, choosing not to keep any settings which is a nice option I never noticed before...I then made sure that the folders for it in Programs and Users were completely deleted. I cleared all my temp files and rebooted, then installed it. When I went to run it, I ran into the same problem again. When it tries to open File Explorer to open local files, it crashed. I opened a file from the cloud just fine, then tried FILE>Open and again it crashed just as it had been. I kind of expected a complete reinstall to fix it but it didn't. Illustrator works just fine so I'm stumped. ONLY photoshop and photoshop beta do this. No other software on my system does it. I thought it might have something to do with some brushes and such that I manually dropped in at some point or some old assets that are no longer compatible but the clean install eliminated that as a problem. The only other thing I can think of is that even though I completely uninstalled it, there might be some registry settings that incorrectly point to explorer but I don't know where those would be. I ran the compatibility checker just to make sure, even though this problem doesn't indicate a GPU issue and it tests fine, all green. Pass: DirectX available Pass: DirectX feature level 12.1 available, feature level 12.0 required Pass: Above required VRAM (8570 MB of 1500 MB required) GPU Detected: Intel(R) UHD Graphics (INTEL) I don't run into any other problems at all. Everything else works as it should. I didn't have this problem until I decided to wipe my Win10 system and do a clean install of Win11. I decided to try something else... I installed v22.2. It works fine. v25.1 - no problems v25.4 - no problems v25.5.1 - no problems v25.6 - no problems v25.7 - no problems v25.9 - no problems v25.9.1 - no problems v25.11 - crashes with error on FILE>Open roll back to 25.9.1 - no problems SO, clearly the problem is something that changed between 25.9.1 and 25.11 Nothing changed in the system requirements. I saw another post with someone with the same error who was told that the problem was systenm requirements due to only having a 1GB dedicated graphics 'card and that they needed to roll back, but this isnt correct. My laptop is only 2 yrs old and it ran under Win10. The specs when I load the intel graphics software show 128MB dedicated/8GB shared memory for the memory adapter. The machine itself has 16GB total and plenty of space available on the SSD for vRAM. It worked fine under Win10 and this happens with or without graphics acceleration active. Aside from that, no hardware requirement changes happened between 25.9.1 and 25.11 but this is where the problem occurs. So the question is.... what DID change? Where is it reading 1GB of graphics memory if my specs are 128MB dedicated/8GB shared? If it were really an actual graphics or memory problem, why does the problem occur on FILE>Open and not elsewhere? Why does it run just fine when opening files directly from Explorer? It seems to me that something changed with the path for Explorer and PS just isn't finding it. Here's the error report in case it's useful to someone... <?xml version="1.0"?> <!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd"> <crashreport serviceVersion="16.7.0.202408221003_c7c60a5" clientVersion="16.7.0.202408221003_c7c60a5" applicationName="Adobe Photoshop" applicationVersion="26.3.0" build="20250122.r.156" source="Windows-Client" crashType="n/a"> <time year="2025" month="2" day="24" hour="11" minute="0" second="12" timeoffset="-360" timezone="Central Standard Time" crsessionduration="63"/> <user guid="049d7c67-ffee-461e-9025-03524992071d"/> <system platform="Windows 11 Pro" osversion="11.0" osbuild="26100" applicationlanguage="en-us" userlanguage="en-US" oslanguage="en-US" ram="16102" machine="Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz" model="Intel64 Family 6 Model 142 Stepping 12" cpuCount="8" cpuType="8664" cpuFreq="2112 MHz" processorArchitecture="9"/> <gpu> <gpuinfo availability="Running/Full Power" adapterCompatibility="Intel Corporation" adapterRAM="1024 MB" caption="Intel(R) UHD Graphics" description="Intel(R) UHD Graphics" driverDate="20240813000000.000000-000" driverVersion="31.0.101.2130" videoModeDescription="1920 x 1080 x 4294967296 colors" pnpDeviceID="PCI\VEN_8086&DEV_9B41&SUBSYS_22BE17AA&REV_02\3&11583659&1&10" installedDisplayDrivers="igd10iumd64.dll,igd12umd64.dll,igdumdim64.dll"/> </gpu> <crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x00007FF77489ACA8"> <backtrace crashedThread="0"> <thread index="0"> <stackStatement index="0" address="0x00007FF77489ACA8" symbolname="WREncodingMap::GetUTFMapping"/> <stackStatement index="1" address="0x00007FF77489E066" symbolname="InputOutputHBImpl::getOutputRuns"/> <stackStatement index="2" address="0x00007FF774870F83" symbolname="IWRFontAccess::CheckFontList"/> <stackStatement index="3" address="0x00007FF77666FD34" symbolname="OptycaSegment::GetWidth"/> <stackStatement index="4" address="0x00007FF779552623" symbolname="OptycaImpl::SetSpacingToFit"/> <stackStatement index="5" address="0x00007FF779653391" symbolname="OptycaImpl::SetSpacingToFit"/> <stackStatement index="6" address="0x00007FF779549320" symbolname="OptycaImpl::SetSpacingToFit"/> <stackStatement index="7" address="0x00007FF779549464" symbolname="OptycaImpl::SetSpacingToFit"/> <stackStatement index="8" address="0x00007FF77486DD4B" symbolname="IWRFontAccess::WRSearchFont"/> <stackStatement index="9" address="0x00007FF7754607B6" symbolname="OptycaSegment::SetCharCount"/> <stackStatement index="10" address="0x00007FF77959C012" symbolname="OptycaImpl::SetSpacingToFit"/> <stackStatement index="11" address="0x00007FF77959FBB7" symbolname="OptycaImpl::SetSpacingToFit"/> <stackStatement index="12" address="0x00007FF77959F493" symbolname="OptycaImpl::SetSpacingToFit"/> <stackStatement index="13" address="0x00007FF77956C2C6" symbolname="OptycaImpl::SetSpacingToFit"/> <stackStatement index="14" address="0x00007FF77488E5BD" symbolname="boost::serialization::singleton<boost::serialization::extended_type_info_typeid<dbrush_0011011100::BrushLibrary> >::singleton<boost::serialization::extended_type_info_typeid<dbrush_0011011100::BrushLibrary> >"/> <stackStatement index="15" address="0x00007FF774863F81" symbolname="IWRFontAccess::WRGetHorizontalMetrics"/> <stackStatement index="16" address="0x00007FF774877E7D" symbolname="boost::serialization::singleton<boost::serialization::extended_type_info_typeid<dbrush_0011011100::BrushLibrary> >::singleton<boost::serialization::extended_type_info_typeid<dbrush_0011011100::BrushLibrary> >"/> <stackStatement index="17" address="0x00007FF7749DC814" symbolname="WRStrSafe::sprintf"/> <stackStatement index="18" address="0x00007FF7748678AD" symbolname="IWRFontAccess::WRGetHorizontalMetrics"/> <stackStatement index="19" address="0x00007FF7765F5D52" symbolname="OptycaSegment::GetWidth"/> <stackStatement index="20" address="0x00007FF97A89E8D7" symbolname="BaseThreadInitThunk"/> <stackStatement index="21" address="0x00007FF97AE7BF2C" symbolname="RtlUserThreadStart"/> </thread> </backtrace> <registerSet> <register name="RAX" value="0x0000000000000000"/> <register name="RBX" value="0x0000000000000028"/> <register name="RCX" value="0x0000000000000000"/> <register name="RDX" value="0x0000000000000000"/> <register name="RSI" value="0x000000000000FFFF"/> <register name="RDI" value="0x0000000000000028"/> <register name="RSP" value="0x00000001000FD3D0"/> <register name="RBP" value="0x00000001000FD6D0"/> <register name="RIP" value="0x00007FF77489ACA8"/> <register name="EFL" value="0x0000000000010206"/> <register name="LastExceptionToRip" value="0x0000000000000000"/> <register name="LastExceptionFromRip" value="0x0000000000000000"/> </registerSet> <binaryImageSet> <binaryImage start="0x00007FF774060000" end="0x00007FF77FA5E000" path="adobe\Photoshop.exe" version="26.3.0.156"/> <binaryImage start="0x00007FF97ADC0000" end="0x00007FF97B023000" path="ntdll.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF97A870000" end="0x00007FF97A937000" path="kernel32.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF978220000" end="0x00007FF9785E7000" path="KERNELBASE.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF974880000" end="0x00007FF97491C000" path="apphelp.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF965310000" end="0x00007FF965374000" path="AcGenral.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF979E40000" end="0x00007FF979EE9000" path="msvcrt.dll" version="7.0.26100.1882"/> <binaryImage start="0x00007FF978C00000" end="0x00007FF978CA6000" path="sechost.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF979EF0000" end="0x00007FF979F4D000" path="shlwapi.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF978CB0000" end="0x00007FF978E79000" path="user32.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF978160000" end="0x00007FF978187000" path="win32u.dll" version="6.2.26100.3194"/> <binaryImage start="0x00007FF979900000" end="0x00007FF97992A000" path="gdi32.dll" version="6.2.26100.2033"/> <binaryImage start="0x00007FF9785F0000" end="0x00007FF97871B000" path="gdi32full.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF978B50000" end="0x00007FF978BF3000" path="msvcp_win.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF978880000" end="0x00007FF9789CC000" path="ucrtbase.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF97A120000" end="0x00007FF97A2B5000" path="ole32.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF97A2C0000" end="0x00007FF97A63E000" path="combase.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF978F10000" end="0x00007FF979026000" path="rpcrt4.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF97ABD0000" end="0x00007FF97AC84000" path="advapi32.dll" version="6.2.26100.2033"/> <binaryImage start="0x00007FF97AC90000" end="0x00007FF97AD79000" path="SHCore.dll" version="6.2.26100.3194"/> <binaryImage start="0x00007FF9791C0000" end="0x00007FF9798C4000" path="shell32.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF9775F0000" end="0x00007FF97761B000" path="userenv.dll" version="6.2.26100.2454"/> <binaryImage start="0x00007FF95C470000" end="0x00007FF95C491000" path="mpr.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF977300000" end="0x00007FF977348000" path="sspicli.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF97A0E0000" end="0x00007FF97A10F000" path="imm32.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF978190000" end="0x00007FF97820F000" path="wintrust.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF979930000" end="0x00007FF9799A4000" path="ws2_32.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF9789D0000" end="0x00007FF978B46000" path="crypt32.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF9799B0000" end="0x00007FF979E36000" path="setupapi.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF9652B0000" end="0x00007FF96530B000" path="adobe\tbbmalloc.dll"/> <binaryImage start="0x00007FF965220000" end="0x00007FF9652A7000" path="adobe\tbb12.dll"/> <binaryImage start="0x00007FF964F40000" end="0x00007FF964F7F000" path="adobe\CITThreading.dll"/> <binaryImage start="0x00007FF964EA0000" end="0x00007FF964F40000" path="adobe\aif.dll"/> <binaryImage start="0x00007FF9722E0000" end="0x00007FF97236D000" path="msvcp140.dll" version="14.40.33816.0"/> <binaryImage start="0x00007FF966800000" end="0x00007FF96681E000" path="VCRUNTIME140.dll" version="14.40.33816.0"/> <binaryImage start="0x00007FF972270000" end="0x00007FF97227C000" path="VCRUNTIME140_1.dll" version="14.40.33816.0"/> <binaryImage start="0x00007FF9415A0000" end="0x00007FF941659000" path="winspool.drv" version="6.2.26100.3037"/> <binaryImage start="0x00007FF964E60000" end="0x00007FF964E94000" path="adobe\AdobePDFSettings.dll"/> <binaryImage start="0x00007FF964D50000" end="0x00007FF964E53000" path="adobe\ZXPSignLib-Minimal.dll"/> <binaryImage start="0x00007FF8BA470000" end="0x00007FF8BA811000" path="adobe\AdobeOwl.dll" version="5.5.0.0"/> <binaryImage start="0x00007FF979030000" end="0x00007FF979106000" path="oleaut32.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF8B9FA0000" end="0x00007FF8BA467000" path="adobe\MPS.dll" version="9.0.0.55924"/> <binaryImage start="0x00007FF8B9C90000" end="0x00007FF8B9F99000" path="adobe\dvaappsupport.dll" version="25.1.0.1"/> <binaryImage start="0x00007FF8B97A0000" end="0x00007FF8B9C82000" path="adobe\dvacore.dll" version="25.1.0.1"/> <binaryImage start="0x00007FF944BC0000" end="0x00007FF944E6C000" path="adobe\dvaworkspace.dll" version="25.1.0.1"/> <binaryImage start="0x00007FF8B9410000" end="0x00007FF8B979D000" path="adobe\VulcanControl.dll" version="7.2.0.34"/> <binaryImage start="0x00007FF964900000" end="0x00007FF9649EB000" path="adobe\VulcanMessage5.dll" version="7.2.0.34"/> <binaryImage start="0x00007FF9545D0000" end="0x00007FF954738000" path="adobe\icucnv74.dll" version="74.2.0.0"/> <binaryImage start="0x00007FF8B8FD0000" end="0x00007FF8B940F000" path="adobe\dvaadameve.dll" version="25.1.0.1"/> <binaryImage start="0x00007FF8B8A30000" end="0x00007FF8B8FC2000" path="adobe\PlugPlugOwl.dll" version="12.0.0.14"/> <binaryImage start="0x00007FF974B90000" end="0x00007FF974CBC000" path="dxgi.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF8B8880000" end="0x00007FF8B8A26000" path="adobe\LogSession.dll" version="8.2.0.16"/> <binaryImage start="0x00007FF8B86C0000" end="0x00007FF8B887B000" path="adobe\CRClient.dll" version="16.7.0.0"/> <binaryImage start="0x00007FF8B8070000" end="0x00007FF8B86BB000" path="adobe\AdbePM.dll"/> <binaryImage start="0x00007FF8B68E0000" end="0x00007FF8B806C000" path="adobe\opencv_world452.dll" version="4.5.2.0"/> <binaryImage start="0x00007FF979FE0000" end="0x00007FF97A0CF000" path="comdlg32.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF8B5060000" end="0x00007FF8B68D3000" path="adobe\mkl_sequential.2.dll" version="2022.1.1.0"/> <binaryImage start="0x00007FF9648C0000" end="0x00007FF9648F5000" path="adobe\act_tracing.dll" version="1.0.58.0"/> <binaryImage start="0x00007FF967350000" end="0x00007FF96751B000" path="GdiPlus.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF96BD80000" end="0x00007FF96BE40000" path="mscms.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF92AE80000" end="0x00007FF92AE88000" path="msimg32.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF8B4ED0000" end="0x00007FF8B505F000" path="adobe\AdobeXMPFiles.dll" version="9.3.3.55945"/> <binaryImage start="0x00007FF8B4BD0000" end="0x00007FF8B4EC3000" path="adobe\AID.dll" version="1.0.0.58"/> <binaryImage start="0x00007FF8B2B20000" end="0x00007FF8B4BD0000" path="adobe\dvaui.dll" version="25.1.0.1"/> <binaryImage start="0x00007FF964860000" end="0x00007FF9648BC000" path="adobe\AdobeSVGAGM.dll" version="4.0.0.55982"/> <binaryImage start="0x00007FF8B0C30000" end="0x00007FF8B2B14000" path="adobe\libdynamic-napi.dll"/> <binaryImage start="0x00007FF940020000" end="0x00007FF9400C8000" path="adobe\JP2KLib.dll" version="4.0.2.55964"/> <binaryImage start="0x00007FF96F880000" end="0x00007FF96F88F000" path="adobe\dnssd.dll" version="3.0.0.2"/> <binaryImage start="0x00007FF954580000" end="0x00007FF9545CA000" path="adobe\WinRTSupport.dll" version="1.0.1.0"/> <binaryImage start="0x00007FF8B0B20000" end="0x00007FF8B0C26000" path="adobe\ExtendScript.dll" version="4.5.12.1"/> <binaryImage start="0x00007FF976DC0000" end="0x00007FF976E0E000" path="powrprof.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF9722D0000" end="0x00007FF9722D7000" path="MSVCP140_CODECVT_IDS.dll" version="14.40.33816.0"/> <binaryImage start="0x00007FF974870000" end="0x00007FF97487D000" path="secur32.dll" version="6.2.26100.1"/> <binaryImage start="0x00007FF972370000" end="0x00007FF97237B000" path="SensApi.dll" version="6.2.26100.1"/> <binaryImage start="0x00007FF977A90000" end="0x00007FF977AB6000" path="bcrypt.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF96BBC0000" end="0x00007FF96BCDE000" path="winhttp.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF95F3A0000" end="0x00007FF95F623000" path="wininet.dll" version="11.0.26100.3037"/> <binaryImage start="0x00007FF8B0A20000" end="0x00007FF8B0B1C000" path="adobe\ScCore.dll" version="4.5.12.1"/> <binaryImage start="0x00007FF951570000" end="0x00007FF951593000" path="D3D12.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF972D40000" end="0x00007FF9731BF000" path="D3DCOMPILER_47.dll" version="6.2.26100.3194"/> <binaryImage start="0x00007FF973CC0000" end="0x00007FF973F1E000" path="d3d11.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF8B0850000" end="0x00007FF8B0A1F000" path="adobe\icuuc74.dll" version="74.2.0.0"/> <binaryImage start="0x00007FF8B0760000" end="0x00007FF8B084E000" path="adobe\AdobeLinguistic.dll" version="16.0.0.0"/> <binaryImage start="0x00007FF976B40000" end="0x00007FF976B72000" path="IPHLPAPI.DLL" version="6.2.26100.3194"/> <binaryImage start="0x00007FF95EE50000" end="0x00007FF95EE6A000" path="netapi32.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF93A580000" end="0x00007FF93A5FC000" path="oleacc.dll" version="7.2.26100.3037"/> <binaryImage start="0x00007FF932890000" end="0x00007FF9328E8000" path="adobe\ARE.dll" version="4.0.0.55982"/> <binaryImage start="0x0000000073350000" end="0x0000000073408000" path="adobe\AXEDOMCore.dll" version="6.1.0.54922"/> <binaryImage start="0x00007FF973A50000" end="0x00007FF973CB9000" path="DWrite.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF977DF0000" end="0x00007FF977E4F000" path="cfgmgr32.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF8AFB00000" end="0x00007FF8B0751000" path="adobe\onnxruntime.dll" version="1.17.24.223"/> <binaryImage start="0x00007FF977550000" end="0x00007FF9775BA000" path="mswsock.dll" version="6.2.26100.3194"/> <binaryImage start="0x00007FF967010000" end="0x00007FF9672A0000" path="comctl32.dll" version="6.10.26100.3037"/> <binaryImage start="0x00007FF973F30000" end="0x00007FF974155000" path="dcomp.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF974CE0000" end="0x00007FF974D0E000" path="dwmapi.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF973410000" end="0x00007FF973A4A000" path="d2d1.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF974DC0000" end="0x00007FF974DD6000" path="wtsapi32.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF8AF600000" end="0x00007FF8AFAF6000" path="adobe\libcrypto-3-x64.dll" version="3.0.14.0"/> <binaryImage start="0x00007FF8AF4B0000" end="0x00007FF8AF5FA000" path="adobe\dvanet.dll" version="25.1.0.1"/> <binaryImage start="0x00007FF9319D0000" end="0x00007FF931A2A000" path="adobe\dvavulcansupport.dll" version="25.1.0.1"/> <binaryImage start="0x00007FF8AE740000" end="0x00007FF8AF4A9000" path="adobe\DirectML.dll" version="1.13.1.0"/> <binaryImage start="0x00007FF96A020000" end="0x00007FF96A02B000" path="version.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF975840000" end="0x00007FF975A81000" path="dbghelp.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF9651F0000" end="0x00007FF965219000" path="adobe\libzip.dll"/> <binaryImage start="0x00007FF8AE4B0000" end="0x00007FF8AE73F000" path="adobe\dvascripting.dll" version="25.1.0.1"/> <binaryImage start="0x00007FF9315C0000" end="0x00007FF93168C000" path="adobe\boost_regex.dll"/> <binaryImage start="0x00007FF955370000" end="0x00007FF955397000" path="adobe\ippcv.dll" version="2021.6.0.1069"/> <binaryImage start="0x00007FF8AD980000" end="0x00007FF8AE4AE000" path="adobe\AIDE.dll" version="6.3.1.55963"/> <binaryImage start="0x00007FF9552E0000" end="0x00007FF9552FA000" path="adobe\ippcore.dll" version="2021.6.0.1052"/> <binaryImage start="0x00007FF8AD520000" end="0x00007FF8AD977000" path="adobe\libmmd.dll" version="20.0.0.0"/> <binaryImage start="0x00007FF8F3A10000" end="0x00007FF8F3A76000" path="adobe\ippi.dll" version="2021.6.0.1083"/> <binaryImage start="0x00007FF9547B0000" end="0x00007FF9547D0000" path="adobe\ippcc.dll" version="2021.6.0.992"/> <binaryImage start="0x00007FF954540000" end="0x00007FF954575000" path="adobe\ipps.dll" version="2021.6.0.1087"/> <binaryImage start="0x00007FF954790000" end="0x00007FF9547AD000" path="adobe\ippvm.dll" version="2021.6.0.1004"/> <binaryImage start="0x00007FF8AD3E0000" end="0x00007FF8AD512000" path="adobe\AdobeXMP.dll" version="9.1.2.55945"/> <binaryImage start="0x00007FF946A50000" end="0x00007FF946B5C000" path="opengl32.dll" version="6.2.26100.1882"/> <binaryImage start="0x0000000072F50000" end="0x0000000073349000" path="adobe\SVGRE.dll" version="9.3.0.55982"/> <binaryImage start="0x00007FF9672B0000" end="0x00007FF9672E6000" path="winmm.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF967970000" end="0x00007FF967984000" path="MSVCP140_ATOMIC_WAIT.dll" version="14.40.33816.0"/> <binaryImage start="0x00007FF9745B0000" end="0x00007FF9746D6000" path="CoreMessaging.dll" version="6.2.26100.3194"/> <binaryImage start="0x00007FF977900000" end="0x00007FF97791C000" path="cryptsp.dll" version="6.2.26100.2454"/> <binaryImage start="0x00007FF8A97B0000" end="0x00007FF8AD3DB000" path="adobe\dynamic-torqnative.dll" version="8.1.1.0"/> <binaryImage start="0x00007FF977060000" end="0x00007FF97707A000" path="kernel.appcore.dll" version="6.2.26100.1591"/> <binaryImage start="0x00007FF972D20000" end="0x00007FF972D39000" path="Microsoft.Internal.WarpPal.dll"/> <binaryImage start="0x00007FF94C8B0000" end="0x00007FF94C8CC000" path="adobe\boost_thread.dll"/> <binaryImage start="0x00007FF94C880000" end="0x00007FF94C8A3000" path="adobe\boost_filesystem.dll"/> <binaryImage start="0x00007FF9731D0000" end="0x00007FF9733FE000" path="WindowsCodecs.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF9469E0000" end="0x00007FF946A0D000" path="glu32.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF93EC40000" end="0x00007FF93EC5C000" path="credui.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF975090000" end="0x00007FF97518B000" path="propsys.dll" version="7.0.26100.3037"/> <binaryImage start="0x00007FF933500000" end="0x00007FF933539000" path="dbgcore.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF972030000" end="0x00007FF972190000" path="dsreg.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF975410000" end="0x00007FF975457000" path="DXCore.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF977780000" end="0x00007FF97778C000" path="CRYPTBASE.DLL" version="6.2.26100.2894"/> <binaryImage start="0x00007FF9767F0000" end="0x00007FF9767FD000" path="netutils.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF977E80000" end="0x00007FF977E8A000" path="dpapi.dll" version="6.2.26100.1"/> <binaryImage start="0x00007FF8A8290000" end="0x00007FF8A97B0000" path="adobe\svml_dispmd.dll" version="20.0.0.0"/> <binaryImage start="0x000001C8A8850000" end="0x000001C8AAB21000" path="adobe\icudt74.dll"/> <binaryImage start="0x00007FF978720000" end="0x00007FF9787B9000" path="bcryptPrimitives.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF974B30000" end="0x00007FF974B8C000" path="directxdatabasehelper.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF974990000" end="0x00007FF974A3D000" path="uxtheme.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF977960000" end="0x00007FF977973000" path="msasn1.dll" version="6.2.26100.2894"/> <binaryImage start="0x00007FF976DA0000" end="0x00007FF976DB4000" path="umpdc.dll" version="6.2.26100.1301"/> <binaryImage start="0x00007FF942860000" end="0x00007FF9428D9000" path="ninput.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF975E40000" end="0x00007FF976677000" path="windows.storage.dll" version="6.2.26100.3194"/> <binaryImage start="0x00007FF968F30000" end="0x00007FF968F3E000" path="adobe\PSRes.dll" version="26.3.0.156"/> <binaryImage start="0x00007FF9679A0000" end="0x00007FF9679A4000" path="adobe\PSViews.dll" version="26.3.0.156"/> <binaryImage start="0x00007FF97A660000" end="0x00007FF97A708000" path="clbcatq.dll" version="2001.12.10941.16384"/> <binaryImage start="0x00007FF978070000" end="0x00007FF97809E000" path="profapi.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF974DA0000" end="0x00007FF974DB2000" path="wbemprox.dll" version="6.2.26100.1000"/> <binaryImage start="0x00007FF974D20000" end="0x00007FF974D9A000" path="wbemcomn.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF969920000" end="0x00007FF969935000" path="wbemsvc.dll" version="6.2.26100.1000"/> <binaryImage start="0x00007FF969B40000" end="0x00007FF969C30000" path="fastprox.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF969220000" end="0x00007FF96923D000" path="amsi.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF969160000" end="0x00007FF9691E3000" path="MpOAV.dll" version="4.18.24090.11"/> <binaryImage start="0x00007FF976FC0000" end="0x00007FF976FF8000" path="rsaenh.dll" version="6.2.26100.2894"/> <binaryImage start="0x00007FF94F370000" end="0x00007FF94F422000" path="Windows.FileExplorer.Common.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF9714B0000" end="0x00007FF971618000" path="WinTypes.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF97AB10000" end="0x00007FF97AB30000" path="imagehlp.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF933360000" end="0x00007FF9333B3000" path="sti.dll" version="6.2.26100.2161"/> <binaryImage start="0x00007FF97A710000" end="0x00007FF97A86C000" path="msctf.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF95CD90000" end="0x00007FF95CD9B000" path="wiatrace.dll" version="6.2.26100.2161"/> <binaryImage start="0x00007FF940F00000" end="0x00007FF940F1B000" path="NetworkExplorer.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF94F5B0000" end="0x00007FF94F674000" path="Windows.StateRepositoryPS.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF966850000" end="0x00007FF966895000" path="windows.staterepositoryclient.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF94E6F0000" end="0x00007FF94E719000" path="edputil.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF96B9F0000" end="0x00007FF96BA81000" path="Windows.Graphics.dll" version="6.2.26100.2454"/> <binaryImage start="0x00007FF95C190000" end="0x00007FF95C36C000" path="urlmon.dll" version="11.0.26100.3194"/> <binaryImage start="0x00007FF95BEC0000" end="0x00007FF95C189000" path="iertutil.dll" version="11.0.26100.3037"/> <binaryImage start="0x00007FF95CA10000" end="0x00007FF95CA39000" path="srvcli.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF94E720000" end="0x00007FF94E74E000" path="cldapi.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF95CB50000" end="0x00007FF95CB67000" path="virtdisk.dll" version="6.2.26100.1591"/> <binaryImage start="0x00007FF977820000" end="0x00007FF97787D000" path="wldp.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF941850000" end="0x00007FF9418AA000" path="dataexchange.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF96A6D0000" end="0x00007FF96A908000" path="twinapi.appcore.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF9412E0000" end="0x00007FF94138D000" path="TextShaping.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF9775C0000" end="0x00007FF9775E7000" path="gpapi.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF9556A0000" end="0x00007FF9556DB000" path="cryptnet.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF9753B0000" end="0x00007FF9753BE000" path="winnsi.dll" version="6.2.26100.2894"/> <binaryImage start="0x00007FF97ABC0000" end="0x00007FF97ABCA000" path="nsi.dll" version="6.2.26100.2894"/> <binaryImage start="0x00007FF978E90000" end="0x00007FF978F0A000" path="coml2.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF8F42D0000" end="0x00007FF8F430D000" path="C_G18030.DLL" version="6.2.26100.1150"/> <binaryImage start="0x00007FF971620000" end="0x00007FF971685000" path="netprofm.dll" version="6.2.26100.2454"/> <binaryImage start="0x00007FF96A6B0000" end="0x00007FF96A6C9000" path="npmproxy.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF96F8B0000" end="0x00007FF96F8CF000" path="dhcpcsvc6.DLL" version="6.2.26100.3194"/> <binaryImage start="0x00007FF96BCF0000" end="0x00007FF96BD15000" path="dhcpcsvc.dll" version="6.2.26100.3194"/> <binaryImage start="0x00007FF976B80000" end="0x00007FF976CA5000" path="dnsapi.dll" version="6.2.26100.3194"/> <binaryImage start="0x00007FF8DAF50000" end="0x00007FF8DAFCA000" path="adobe\AdobePIP.dll" version="8.2.0.16"/> <binaryImage start="0x00007FF959060000" end="0x00007FF959123000" path="webio.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF96AD50000" end="0x00007FF96AD5B000" path="rasadhlp.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF9707C0000" end="0x00007FF970845000" path="FWPUCLNT.DLL" version="6.2.26100.3037"/> <binaryImage start="0x00007FF976EA0000" end="0x00007FF976F69000" path="schannel.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF977A50000" end="0x00007FF977A80000" path="ncrypt.dll" version="6.2.26100.2894"/> <binaryImage start="0x00007FF977A00000" end="0x00007FF977A3F000" path="ntasn1.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF95EF80000" end="0x00007FF95EFAD000" path="ncryptsslp.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF968D90000" end="0x00007FF968ED6000" path="textinputframework.dll" version="6.2.26100.3194"/> <binaryImage start="0x00007FF970B10000" end="0x00007FF970DF3000" path="CoreUIComponents.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF8A59F0000" end="0x00007FF8A5B2E000" path="adobe\microsoft.ai.machinelearning.dll" version="1.17.24.223"/> <binaryImage start="0x00007FF977DC0000" end="0x00007FF977DED000" path="devobj.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF969530000" end="0x00007FF9697A3000" path="D3D12Core.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF939330000" end="0x00007FF939354000" path="igd12umd64.dll" version="31.0.101.2130"/> <binaryImage start="0x00007FF8A4FA0000" end="0x00007FF8A59E2000" path="igd12um64kbl.dll"/> <binaryImage start="0x00007FF96F8E0000" end="0x00007FF96FCE9000" path="igdgmm64.dll" version="31.0.101.2130"/> <binaryImage start="0x00007FF96C060000" end="0x00007FF96F7F6000" path="igc64.dll" version="31.0.101.2130"/> <binaryImage start="0x00007FF8EDA40000" end="0x00007FF8EDA6E000" path="D3DSCache.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF8CAD70000" end="0x00007FF8CDE58000" path="igd12dxva64.dll" version="31.0.101.2130"/> <binaryImage start="0x00007FF93A550000" end="0x00007FF93A577000" path="igdinfo64.dll"/> <binaryImage start="0x00007FF94D5F0000" end="0x00007FF94DB95000" path="d3d10warp.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF941780000" end="0x00007FF941798000" path="opencl.dll" version="3.0.6.0"/> <binaryImage start="0x00007FF967AF0000" end="0x00007FF967B0A000" path="windows.staterepositorycore.dll" version="6.2.26100.1882"/> <binaryImage start="0x00007FF8A4A40000" end="0x00007FF8A4F95000" path="igdrcl64.dll" version="23.20.101.2130"/> <binaryImage start="0x00007FF8BA990000" end="0x00007FF8BAA94000" path="igdfcl64.dll" version="31.0.101.2130"/> <binaryImage start="0x00007FF89FC50000" end="0x00007FF8A4A35000" path="opencl-clang64.dll" version="2.0.9.0"/> <binaryImage start="0x00007FF966440000" end="0x00007FF966450000" path="adobe\FastCore.8bx" version="26.3.0.156"/> <binaryImage start="0x00007FF8BA8C0000" end="0x00007FF8BA98F000" path="adobe\MMXCore.8bx" version="26.3.0.156"/> <binaryImage start="0x00007FF8CF8E0000" end="0x00007FF8CF974000" path="adobe\MultiProcessor Support.8bx" version="26.3.0.156"/> <binaryImage start="0x00007FF8E7EE0000" end="0x00007FF8E7F26000" path="adobe\Plugin.dll" version="26.3.0.156"/> <binaryImage start="0x00007FF89F2B0000" end="0x00007FF89FC48000" path="adobe\HalideBottlenecks.8bx" version="26.3.0.156"/> <binaryImage start="0x00007FF89EA10000" end="0x00007FF89F2A8000" path="adobe\Dicom.8bi" version="26.3.0.156"/> <binaryImage start="0x000000004FAD0000" end="0x000000005DBA4000" path="adobe\Camera Raw.8bi" version="17.2.0.2155"/> <binaryImage start="0x00007FF977180000" end="0x00007FF9771B5000" path="ntmarta.dll" version="6.2.26100.1150"/> <binaryImage start="0x00007FF96B1C0000" end="0x00007FF96B3CD000" path="mfplat.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF96B0C0000" end="0x00007FF96B101000" path="RTWorkQ.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF8DACD0000" end="0x00007FF8DAEFD000" path="msxml3.dll" version="8.110.26100.3037"/> <binaryImage start="0x00007FF8EC510000" end="0x00007FF8EC535000" path="adobe\BIB.dll" version="4.0.0.55982"/> <binaryImage start="0x00007FF8E56C0000" end="0x00007FF8E56EB000" path="adobe\BIBUtils.dll" version="4.0.0.55982"/> <binaryImage start="0x00007FF89E8C0000" end="0x00007FF89EA03000" path="adobe\ACE.dll" version="6.0.1.55982"/> <binaryImage start="0x00007FF89E1B0000" end="0x00007FF89E8BF000" path="adobe\AGM.dll" version="7.1.0.55982"/> <binaryImage start="0x00007FF89DD60000" end="0x00007FF89E1AE000" path="adobe\CoolType.dll" version="10.0.0.55982"/> <binaryImage start="0x0000000072F20000" end="0x0000000072F4B000" path="adobe\AXE8SharedExpat.dll" version="6.1.0.54922"/> <binaryImage start="0x00007FF899270000" end="0x00007FF89DD5A000" path="adobe\mkl_core.2.dll" version="2022.1.1.0"/> <binaryImage start="0x00007FF8A6610000" end="0x00007FF8A69FE000" path="adobe\ippccl9.dll" version="2021.6.0.992"/> <binaryImage start="0x00007FF8A7C70000" end="0x00007FF8A8281000" path="adobe\ippcvl9.dll" version="2021.6.0.1069"/> <binaryImage start="0x00007FF8A6A00000" end="0x00007FF8A7C64000" path="adobe\ippil9.dll" version="2021.6.0.1083"/> <binaryImage start="0x00007FF8A6080000" end="0x00007FF8A6610000" path="adobe\ippsl9.dll" version="2021.6.0.1087"/> <binaryImage start="0x00007FF8A5B30000" end="0x00007FF8A6076000" path="adobe\ippvml9.dll" version="2021.6.0.1004"/> <binaryImage start="0x00007FF8DAF00000" end="0x00007FF8DAF49000" path="icm32.dll" version="6.2.26100.2314"/> <binaryImage start="0x00007FF898A20000" end="0x00007FF899270000" path="adobe\ScriptingSupport.8li" version="26.3.0.156"/> <binaryImage start="0x00007FF897BD0000" end="0x00007FF898A11000" path="adobe\MaterialSuite.8li"/> <binaryImage start="0x00007FF9769F0000" end="0x00007FF976A50000" path="winsta.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF93B4F0000" end="0x00007FF93B59E000" path="twinapi.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF896D00000" end="0x00007FF8975B0000" path="adobe\AdobeHunspellPlugin.dll" version="16.0.0.0"/> <binaryImage start="0x00007FF896BF0000" end="0x00007FF896CF5000" path="adobe\WRLiloPlugin.dll" version="1.3.14.1"/> <binaryImage start="0x00007FF977FA0000" end="0x00007FF978041000" path="sxs.dll" version="6.2.26100.1"/> <binaryImage start="0x00007FF896130000" end="0x00007FF896BE2000" path="adobe\adobe_c2pa.uxpaddon"/> <binaryImage start="0x00007FF9428E0000" end="0x00007FF94293D000" path="ApplicationTargetedFeatureDatabase.dll" version="6.2.26100.3037"/> <binaryImage start="0x00007FF8DB660000" end="0x00007FF8DBBD4000" path="EmbeddedBrowserWebView.dll" version="133.0.3065.82"/> </binaryImageSet> <dumpType> Mini </dumpType> <hbLogSessionDllStatus> </hbLogSessionDllStatus> </crash> <sessionId> e54bb697-585f-4fe4-9d42-fb32d2424667 </sessionId> </crashreport>
... View more
‎Feb 21, 2025
09:06 PM
What's been done so far: Update dGraphics Drivers: Ensure drivers are up-to-date. Reset Preferences: Hold Ctrl + Alt + Shift while launching Photoshop. Disable Graphics Processor: Uncheck Use Graphics Processor in Preferences > Performance. Reinstall Photoshop: Renamed Workspaces folders at C:\Users....Adobe Photoshop \Adobe Photoshop 2025 Settings \Workspaces ...and workspaces (modified) Renamed C:\Users.....\Adobe Photoshop \Adobe Photoshop Settings to "Adobe Photoshop Settings_old" This last one caused it to run without any preferences setup which caused the backstage or whatever it's called to launch. I don't know as I've always turned that off right away. From there I was able to choose an option to open a new file where I was given a choice - from the cloud account or the local drive. Choosing to open from the cloud actually works. But if I choose to open a local file, it crashes. So it appears that the crash is happening when PS opens Explorer... Which as I said, all works fine as long as I "open with" Photoshop from Explorer. But Apparently PS is crashing when trying to open the Explorer dialog. Since I'm running Beta most of te time and rarely run the current release, I'm going to try backing up its settings folder then reinstalling. I'll run and test then if it works, backup and start moving preferences & settings folders in one at a time. Since nobody seems to have a solution on this, I'll report back how that goes. None of these has resolved it.
... View more
‎Feb 21, 2025
02:09 PM
1 Upvote
I have. To clarify, I know this is something I probably did myself while setting up the system. The only thing I did different from usual installations is that I'm running "StartAllBack" but I never had problems with it before. I'm hoping someone else has run into this because I don't have to reinstall all my brushes and other customizations yet again. It's a nuisance rather than being critical since I can still use it fine as long as I open the images from Explorer. To clarify the problem, here's what I'm running into... If I right-click an image in Explorer and "Open With" and choose Photoshop, everything runs just fine. If I open photoshop and click File. Open recent, and click on a file in the history, it opens fine. File>Browse in Bridge I can open images fine. Other adobe apps work as expected. In Photoshop, if I go to File>Open or File>Open As, it pops up a prompt "Sorry, an error occurred" to submit the error to Adobe and when I do, it shuts down. The error is : <crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x00007FF773A005F8"><backtrace crashedThread="0">
... View more
‎Jan 21, 2025
09:13 AM
Yep. No change. I'm shooting canon so the file extension is .CR2. it's curious because I have them stored in OneDrive and both my Samsung phone and my laptop have no trouble displaying them. I can open them in PS just fine. It's just the export from ACR that fails with the error. It happens in both the public release and the beta which are both up to date. I just did a clean win11 installation in December and ran into this when all I'd installed was Adobe CC and MS Office... Before importing my brushes and workspace backups. I've got the system just about where I want it and did an image backup so if anyone has some ideas to try to fix this I'll be more than happy to play the troubleshooting game.
... View more
‎Jan 10, 2025
10:50 PM
PS Beta 26.3.0 build 20250108.m.2932 PS 26.2.0 Release Lenovo Thinkpad Yoga X1 Carbon Intel i7 Gen11 Win11 Pro - Clean install Dec 15, 2024 Summary: Problem: In both the Beta and Public release, when I open PS and do a FILE>OPEN, PS crashes. I've run chkdsk, SFC, DISM /online /cleanup-image /restorehealth I DO have "StartAllBack" installed although I used it before the restore without this kind of issue. Apps that shouldn't have any bearing on this.... MS Office (word, onedrive, onenote, excel, etc), Picpick, Files Preview, Notebook++ QDir, PhoneLink, Adobe CC (Acrobat, Photoshop (beta+release), illustrator, etc) NexusFile, NexusFont, Acronis backup, Sagethumbs I use a Huion keydial mini K-20 (bluetooth) and a logitech trackball (wireless dongle) Nothing odd, nothing cracked, no reason for this. I'm using a Lenovo ThinkPad X1 Yoga - I7 Gen11. I was running Win10 Pro but when I decided to upgrade the SSD in December I figured I'd do a clean install and on a whim went with Win11 Pro. I built my base system with my most used software, ran updates until everything was up to date, then created a system backup. This includes Photoshop Release and Beta versions. Since then I've been using Photoshop Beta almost exclusively. Normally I'll browse images in Explorer or ACDSee and open them in photoshop either with a right click "open with" or a created shortcut key. So it wasn't until today that I noticed that the basic function of FILE>OPEN causes it to hang, then the popup crash report comes up and when I send, PS closes and I have to re-open it. I was preparing to report it through PS when I thought to check the regular release. It's also up to date as of 18 days ago with no more recent versions available, but it too crashes with a basic FILE>OPEN. Has anyone else run into this?
... View more
‎Jan 10, 2025
04:43 PM
This is quite nice as it makes it a bit easier to navigate fonts but it would be much better if the constant shifting of alignment in the list could be stopped so that scrolling was smooth. The entire experience is stymied by this constant shifting and it's been part of both the production and beta for quite some time. This is a fairly fresh install on Win11 as I finally upgraded a couple weeks ago with a clean install. It's been going on for as long as I can remember across multiple machines. Below is an example. In the first you can see that most of the sample text is at a fixed distance from the font name. In the second, the sample text is aligned separately. I honestly don't care which way it presents, but as it is, it wants to present BOTH ways so the box is constantly resizing and realigning as I scroll through the list of fonts. It's probably my biggest gripe about PS but I don't use fonts often... until this week.
... View more
‎Jan 10, 2025
01:44 PM
I'm fairly certain what you've run into is a myth, possibly via communication errors over time. Fonts as we know them aren't transmitted in a fax as they are with documents saved as files. Fax machines convert scans One of the first and most popular fonts created with faxing in mind was Lucida Fax... which interestingly is a slab serif rather than a sans serif. But it works because of the shapes and specific application of serifs to enhance legibility. Here's some material if you want to delve more deeply into it. Perhaps one of these will lead you to what you're looking for and if you do find it, please let me know. https://lucidafonts.com/blogs/bigelow-holmes-blog/how-and-why-we-designed-lucida https://tug.org/store/lucida/lucida-story.html https://en.wikipedia.org/wiki/Lucida#Lucida_Fax
... View more
‎Jan 06, 2025
10:20 PM
Great to hear it!
... View more
‎Jan 06, 2025
04:26 PM
1 Upvote
This was corrected in beta 23.3.0 20241222.m.2915 <p>Current version is 20250104.m.2928. If you still have this problem, make sure you've updated to the latest version. Also, this IS the BETA version. Problems are gonna happen as new features are continually added and we find them, report them and they fix them. It has no bearing on the final product.
... View more
‎Jan 03, 2025
06:31 AM
Yeah. I thought about that. There's already a function in settings to allocate memory which I would think is much more complex than allocating recovery disk space. So one option would be to simply allow the user to turn it on and off and choose how much disk space to set aside for it. But as I understand it, Photoshop is already saving everything to temp space as it is. I use the beta which at times has crashed while using it and when re-launched, files I was working on were preserved. So the ability to store and recover is already there. All we're really talking about is the ability to manually save it and re-load it as sessions. At least that's my take on it but I'm a long way from an actual software engineer. lol
... View more
‎Jan 03, 2025
05:24 AM
Did that answer the question well enough? If you need more info let me know.
... View more
‎Dec 23, 2024
06:50 AM
Updated to 26.3 Beta to resolve a problem in 26.1. Now I'm unable to open images from Explorer with Photoshop Beta. Nor can I set Photoshop Beta as default for any image type. Instead, when right-clicking an image to "open with" or when selecting a default app for a file type in Windows, PS Beta doesn't appear in the apps list. If I "choose another app" it doesn't come up there either. If I then browse for the app and select Photoshop.exe from the Photoshop Beta folder, the "Choose an app" window just pops open again. I can go through this process over and over and it just loops back every time. Running Win11 24H2 Build 26100.2605 on a lenovo thinkpad intel i7 12700
... View more
‎Dec 20, 2024
12:25 PM
I'm sorry. Not sure how that happened. The problem is that ACR generates an error anytime I try to export raw files to png. Before reporting it I did a search and found this problem to be ongoing for nearly three years. There seem to be other format export conversion errors as well but this is the only one that I ran into. I can provide you with a sample raw file that causes the problem if needed. It does this with every raw file that I have. They're from a Canon 7D.
... View more
‎Dec 18, 2024
08:27 PM
Win 11 24H2 (Build 26100.2605) Photoshop Beta 26.3.0 In versions prior, and in the regular release, after free-transforming a selection I could right-click it and select any of the transform tools such as scal, rotate, skew, warp, etc. I could do this as many times as needed without issue. In 26.3.0 when I do this, I can't get any of the transform tools to come up unless I go to the main menu for them. It was not doing this prior to the 26.3.0. Instead, I can right-click and get the transform tool once. But from there the right click simply fails to pop up. This is a fairly fresh install on a Lenovo Thinkpad X1 Carbon 12th gen. Did a complete reset 2 weeks ago, maybe 2 updates to photoshop since. Everything is up to date on the PC. Anyone else experiencing this?
... View more
‎Dec 18, 2024
10:35 AM
This problem has been ongoing since at least March of 2022. https://community.adobe.com/t5/bridge/ct-p/ct-bridge?page=1&sort=latest_replies&filter=all&lang=all&tabid=discussions It's a basic function and PNG is one of the most popular ways to store and share images since they're lossless and supported by just about everything. It just makes no sense for this problem to continue for years on end. The last couple of years have been a whirlwind of new ideas and updates, some of which have been incredible but before adding more you should really stop and just take a moment to fix the things that are broken.
... View more
‎Dec 04, 2024
07:08 PM
Whoops. Got my wires crossed. lol Mentally I was thinking about when layers became available. It was SO exciting! lol Then my brain took a detour to thinking about the tabs... I'm just not as sharp as I used to be. 😛
... View more
‎Dec 02, 2024
11:44 AM
STILL an issue.... Bridge 15.0.0.357
... View more
‎Nov 28, 2024
10:46 AM
I just had to reset my PC and my backup toolbar file is corrupt which left me having to manually setup my toolbar. I forgot how annoying it is to work with. There are 70+ tools but you can only see 10-11 at a time....if the box is manually expanded to fill the entire height of the screen. If using two columns, every other tool is in the left column but there's no indication of where it is when placing it. Adding or removing one tool can mess up the entire toolbar below it. A simple solution would be to offer a "Compact View" that eliminates all the dead and useless space between the names of each tool. They will ALL fit on one page without the font being too small. If not all, then at least 50 of the 70+ tools would fit just fine. Better would be an optoin for a "layout view" that would reflect the side by side nature of a two-column toolbar. Either way, the ability to only see 10-11 of 70+ tools at a time is just nuts... It reminds me of reviewing bank statements on my old flip phone of two decades ago....
... View more
‎Nov 14, 2024
08:46 AM
I'm not at home right now but I'll upload the entire image when I get home. It was originally a 600 ppi scan of a drawing that he downsized to 72 ppi to use as a desktop icon but rather than save as another file name he just saved it. So he torched that file and lost the original over the years. The rest of the image is easy enough. Mostly straight lines... I'm not so concerned with this image in particular as I am with the methods used in cleaning up this specific type of shape... I guess it would be a curved parallelogram? Lol As I said, I've run into this type of shape several times over the years. I've pretty much only used Photoshop for photography where there's rarely a need for clean lines so I never bothered to figure out a quick solution. It's not critical here either as I probably won't do anything like this again for quite a while. I'm just curious about what methods others use for such things that may be less time-consuming than what I've done in the past.
... View more
‎Nov 13, 2024
07:43 PM
I've run into this frequently over the years and I'm just finally getting around to asking. I'm working on cleaning up an image which was resized from a smaller image. Here's part of it. As you can see, there are curved lines and straight parallel lines. To clean it up I've tried a number of things over the years... select color range, pen tool, curvature tool, and other such things. I've tried painting selections as well. I've probably done it a dozen different ways but I can't escape the feeling that I'm putting far more effort into it than I need to be. So I thought I would ask here... what's the easiest method to clean this up so that it has nice, clean lines?
... View more
‎Oct 10, 2024
06:59 AM
It would be great, and possibly would allow for more accurate "reading of text" if there was an option button to choose fonts from an adobe typeface. I know this is a tall ask requiring a deep look at the underlying code, but it would also likely solve the general AI issue of being poor at generating text. Basically, if the option button for text is checked, a subroutine would be inacted that ran text recognition and then replaced the recognized text with real text from a font database..... Having it run only when a user selects a radio button would prevent other elements from being recognized as text and help it to learn. just a thought. 🙂
... View more
‎Oct 10, 2024
06:21 AM
I think one of the problems is that to simply add text to a pdf within the regular text of the document rather than an overlay which may or may not match, Acrobat has to do optical character recognition. When that is done, adding/editing text can be very frustrating. I recently ran across this when I wanted to update my resume and the only copy I could find was a pdf. It was downright horrid and after messing around with it for over an hour trying to edit one sentence and add another, I gave up and retyped the entire thing. Exporting to word just made a terrible mess of formatting making it just as impossible to edit. Acrobat just isn't meant for editing things like a word processor document. It does fine when you need to edit a simple flyer or basic text, but with things like resumes, invoices, bill statements, etc.... anything with tables.... there are just so many sources that it's near impossible to reverse engineer them. That's something that Acrobat just can't do.... Yet. This is where AI can be used to make a world of difference. I think it would be great if there were an option to reverse engineer documents. If an AI could be trained to recognize paragraph indents, spacing, tables, fonts, layouts, etc, it could make this awkward work much easier. You could choose "Document Reconstruction" from the menu, define a source such as MS Word, and it could break down the document as if it were an MS Word document. This would be a POWERFUL new tool! Now that I'm thinking about it, this is what it should do when exporting as a Word document. lol When exporting as a document type, it should run through AI to check and make sure that the exported document will actually appear the same as the pdf. Right now, more often than not when I export something to a Word document it's more often than not, a complete mess. The same when exporting to Excel. Rather than exporting, then looking at the exported result in disappointment, it needs to use Ai to internally generate the document, compare its appearance to the pdf and if it isn't right, edit.... over and over until it DOES appear the same as the document. This would be amazing and would solve me and a lot of others a LOT of trouble.
... View more
‎Jun 26, 2024
10:53 AM
1 Upvote
For those unable to find the place to edit their Community Avatar image and just want a quick answer, The Adobe Community Avatar image is can be changed on the VIEW COMMUNITY PROFILE page, NOT the "Edit Community Profile" page. For quite some time I've had a custom avatar for my Adobe account but in the discussion forums, it remained this: I was about to post a gripe about it as I've seen many others do, but seeing that some people had custom avatars in the Community, I decided there had to be a way to do it and I finally had some time today to dig in and sort it out. I thought I'd share and hopefully get a fix for what I think is simply an overlooked error. I'll describe it as best that I can... The Community Profile and the Account Profile use separate images. While the Account Profile image is simple to change, the Community Profile is a mess. To change the Account Profile avatar, clicking the avatar in the top right and then "manage account" on the menu takes you to a page that allows the account info and the avatar to be changed. Simple.... Just below that is a section for the Adobe Community. There it has "View Community Profile", "Edit Community Profile", and "Help". Basic user skills suggest that changing the avatar for the Community Profile would be just as simple... Click the "Edit Community Profile" section and edit. But that's not how it works. Instead, when "Edit Community Profile" is clicked, the Communuty Profile page loads which shows the following at the top: Community profile "Your profile photo and name are managed through your Adobe Account. This information is visible to others and can be different from your account name if you choose. You can update your Public Profile at any time and it will automatically update anywhere your profile photo and name appear." Below that is a box with the currently chosen Community Avatar on the left, the Adobe Account screen name, Community screen name, email, and company. NONE of these can actually be edited here. On the right side of the box is a nice button that says "Edit on Adobe Account". Occupation, signature, and time zone are in a second box below that are all editable. Settings for notifications, folllowing threads, and an entire tabbed page is there under preferences for nothing more than typing in how many threads you want on a page. Both the in-line hyperlink and the button in the Community Profile at the top of the "Edit Community Profile" page take the user to the Adobe Account Profile editing page. There, the user sees the Account Avatar, then probably thinks as I did...."Well, I've already set my avatar so apparently something is screwed up on Adobe's side so I'll try another time.". Or they try to edit it and then come back to the Community to be faced again with the previous avatar image. The Community Avatar, Community Screen name, and Company name cannot be edited in the "Edit Community Profile" section! The Screen name and Company name can be edited by following the link, so that's not a big deal. But the Community Avatar can't be edited there. Instead, to EDIT the Community Avatar, one has to go to the VIEW COMMUNITY PROFILE page by clicking on the tiny editing icon on the top-right of the Community Avatar image. This is just bizarre. At the very least, why not make the Avatar image on the "Edit Community Profile" page a hyperlink to the same edit page that is reached by clicking the icon on the "View Community Profile" page? If there's something that makes this too complex, then at the very least, a "Click here to edit your Community Profile avatar" link should do the job just fine. I can't imagine it taking more than a couple minutes no matter how complex the site is.
... View more
‎Apr 23, 2024
02:55 PM
1 Upvote
PS Beta 25.8.0 Win10 Pro 19045.4353 Feature Experience Pack 120.2212.3920.0 I can't say for sure when I noticed this but sometime in the last few months, the "Subject Selection" has been giving me strange random holes in subjects selected that it wasn't doing last year. I'm not sure sure if it's specific to the beta or happening in the regular release as well. I'll do some further testing later with the regular release. I've been working to reproduce it consistently enough to predict it but not having a lot of success. I can't find anything consistent. For example, making an adjustment in ACR either way may or may not increase, decrease or even relocate holes in the selection. Common sense would tell me that this might happen with an area that's either blown out or horribly underexposed but it doesn't seem to trend towards one or the other. Nothing in the spot(s) unselected indicates that it's anything but random. If anything it tends to lean a bit towards middle grey but that's speculation I have yet to start tracking. To add to it, making changes to the image and then selecting the subject again will often change the spot(s) sizes and locations, but not always. When it moves and reshapes, nothing in the colors has changed at all. Resizing also impacts it but in no predictable way. Scale up or down and the holes will move to other random places and in other shapes. Scale up a 1200 ppi image to 2400, different result. Downsize it back to 1200 and the holes will appear in different places. But undo back to the the previous and select the subject again and it reselects the same area as though there is "something" specific triggering it. Save it, close PS, relaunch, open the image, select subject and again the same holes in the same shapes and places. Save it as a bitmap, jpeg, psd, png, it almost doesn't matter. But save it as a gif, close it, open the gif, change the mode to RGB and it will select the item without problem. But then it only has 256 colors. So the complex color information seemed to be the underlying issue. So I converted to greyscal and tried again. It STILL left holes but in a different place. Adjusting the sliders when converting to black & White will alter the shape and location but the shade of grey selected is never the same. I'm at a complete loss trying to find some kind of recognizable cause or a sensible workaround. There's no pattern I can discern. Anytime I come up with a new hypothesis, it gets proven wrong almost immediately. The one thing that has seemed to do it is to push the exposure up in ACR until the whites all over begin to blow out which isn't a solution. I know... simple... "just add to the selection with the lasso."... lol But after working with Adobe the last 26 years or so I want to help when and where I can. 🙂 I've spent about 30 hours the last two weeks trying to nail this one down though and I'm stumped. Here's some examples. I had several more but the board limited me to 10 images. Note: These are not my images. Some are my daughters and the others are grabs off the internet as I wanted to try white silk for testing. I'm pretty sure that troubleshooting using public images constitutes fair use. I put some notes in the images themselves when I uploaded them. Not sure where they display. selection change depending on outside cropped area. Note the small blue section on her left shoulder is not deselected here. a bit more right arm cutting the shoulder off resulted in the hole vanishing. expanding to a place somewhere between the two gave this mess. Still missing the blue sky in the hair though. selection change depending on outside cropped area. This is almost right. It DID select the blue sky seen through the hair. But it did leave a tiny hole in the right armpit. Easy enough to deal with but why? more neck but less bottom resulted in this. smaller 300ppi image from my daughter's phone. This is not blown out at all. Moved to ACR and reduced exposure. Result is more area of a roughly middle grey delected along with the lower left portion. back and reran the select subject tool Pushed exposure UP in ACR. problem disappeared. note the center-left area is now blown out and detail is lost. So lack of detail is not a trigger.
... View more
‎Mar 18, 2024
06:30 PM
2 Upvotes
There have been a lot of requests for similar functionality but curious what you're after specifically. For example, I'd like to see this whole concept reworked so that we not only get filenames, but in the list on hover it would pop up the image. We could multi select them, not just shift-select, but CTRL+ as well. Additionally nice would be session saving where one could save a session or project with certain images open, then close it out, open other things and work, then later launch that same session once again. It should work the same way in open files where hovering over the tab provides a popup of the image which would be especially useful when lots of smaller files are open at once in tabs extending beyond what can be seen.
... View more
‎Oct 18, 2023
08:34 AM
1 Upvote
Thanks for the tip. Unfortunately, it doesn't seem to allow me to upvote my own post.
... View more
‎Oct 03, 2023
05:51 PM
1 Upvote
This is likely a very old Windows bug that seems to have no rhyme or reason. It not only happens on the desktop but also in the Downloads folder and less often, in the other Windows folders such as Documents, Pictures, etc. This is becayse these folders aren't actually folders as part of the directory structure but are instead part of the Windows OS and they can be moved and pointed to all sorts of places. So for example, I have OneDrive, OneDrive for business, and my "Documents" folder is on my personal OneDrive with Videos but "Pictures" is located on OneDrive for Business. But they just appear in the same place in Explorer regardless of where you physically located them. But this means that all of these folders have to be interpreted and contents loaded into the mini app....which is apparently a low priority process and gets edged out by other things on occasion and doesn't update. One things that causes a similar behavior for example is downloading a zip file to the downloads folder and unzipping it there. Often it just won't appear. Refresh/f5 doesn't always work, even closing explorer and opening it doesn't always work. Yet if you try to unzip again, it will ask if you want to overwrite the file that you can't see is there. It's bizarre, wonky, and annoying. The solution is to not use those locations to save things. Use File Explorer to put a convenient folder somewhere directly on a drive and put a Quick Access shortcut in File Explorer and/or a shortcut to it on your desktop. it will save you a ton of grief.
... View more