Good idea.   Posted. ... View more

See Jerrery Tranberry's answer above. It should fix your issue.   Install the Media Feature Pack in windows as instructed here:  https://support.microsoft.com/en-us/topic/media-feature-pack-list-for-windows-n-editions-c1c6fffa-d052-8338-7a79-a4bb980a700a ... View more

The resolution on this post fixed this issue:   https://community.adobe.com/t5/photoshop-ecosystem-bugs/p-could-not-initialize-photoshop-because-of-a-disk-error/idc-p/12477954#M28487     ... View more

Can confirm this accepted resolution fixed my issues posted here: https://community.adobe.com/t5/photoshop-ecosystem-bugs/could-not-initialize-photoshop-because-of-a-disc-error/idc-p/12477951#M28486   and here: https://community.adobe.com/t5/camera-raw-bugs/ps-v23-camera-raw-v14-could-not-initialize-photoshop-because-of-a-disc-error/idi-p/12477765#M2067 ... View more

Found the solution here:   https://community.adobe.com/t5/photoshop-ecosystem-bugs/p-could-not-initialize-photoshop-because-of-a-disk-error/idi-p/12475738   Windows was missing the "Media Feature Pack". After installing that and uninstalling/reinstalling photoshop (and camera raw v14 with it) everything works as intended. ... View more

cross-posted this error to the Camera Raw section:   https://community.adobe.com/t5/camera-raw-bugs/ps-v23-camera-raw-v14-could-not-initialize-photoshop-because-of-a-disc-error/idc-p/12477844#M2068   ... View more

Another quick note: Adobe Bridge's ability to display RAW images is broken with the v14 plugin file but works fine with the v13.1 plugin file.   Lightroom Classic must have its own RAW engine separate from Camera Raw. Neither plugin file seems to have any effect LR Classic's ability to work with existing RAW images. ... View more

Note that Adobe Bridge's ability to display RAW images is broken with the v14 plugin file but works fine with the v13.1 plugin file.   Lightroom Classic must have its own RAW engine separate from Camera Raw. Neither plugin file seems to have any effect LR Classic's ability to work with existing RAW images. ... View more

Adding a link to my post in the photoshop section:   https://community.adobe.com/t5/photoshop-ecosystem-bugs/could-not-initialize-photoshop-because-of-a-disc-error/idc-p/12477673#M28461   Photoshop v23 installs with Camera Raw v14 and will not launch. Invalid prefs file error, followed by a generic disc error message. Replacing v14 with v13.1 allows Ps v23 to launch, but camera raw 13.1 sometimes crashes Ps v23. ... View more

2nd update: I have been able to confirm that there's an issue with the camera raw v14.0 that installed along with photoshop v23. Following all instructions here *to the letter*: https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html I made backups as instructed and then cleaned up the current installation of Camera Raw 14, essentially wiping it off of my system. I found that photoshop still runs in this state, but has no RAW support. It should be noted that the CC desktop app also no longer lists Camera Raw as being installed.   I then downloaded v13.1 & 14.0 installers here: https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-in-installer.html   I confirmed after installing v13.1 that photoshop v23 has *buggy* raw support in this state; Camera Raw 13.1 sometimes crashes Photoshop v23. I cannot say that this is entirely unexpected, just making a note of it. I should also note here that the CC desktop app nor the CC cleaner app recognize that v13.1 is installed.   I installed v14.0 again (renaming the v13.1 plugin file to "Camera Raw.8biOLD" again first) and confirmed that once again photoshop gives me the error about an invalid (deleted) preferences file. A second launch displays the next error, unable to initialize due to disc error.   Switching the Camera Raw plugin filenames back around so that the v13.1 is enabled and v14.0 disabled, photoshop launches successfully.  Again, note that CC desktop app still does not list Camera Raw as installed.   --- THERE IS A PROBLEM WITH CAMERA RAW v14.0, at least on some installations ---   System: Windows 10 Enterprise N 10.0.19042 Build 19042 Intel Core i7-7700k 32GB Ram Nvidia Quadro P2000, driver 30.0.14.7141   ... View more

Yes, similar to my update post. Deleting the plugin or renaming it to something else allows photoshop to run as expected, but without RAW file support. ... View more

an update:   If I find the camera raw plugin, "Camera Raw.8bi" in: C:\Program Files\Common Files\Adobe\Plug-Ins\CC\File Formats   and re-name it to something else so photoshop ignores it, like "Camera Raw.8biOLD" then photoshop starts successfully, but it will not open RAW image formats (obviously) What's strange is the CC desktop application reports that camera raw is up to date even after this. ... View more

I updated to v23 this morning and received two errors, the first being about the preferences file being invalid (deleted) despite telling photoshop to import previous settings (which it did, according to what I could find my my windows %appdata% folder for Photoshop 2022).   The second and persistent error is "Could not initialize photoshop because of a disc error". I had it remove old versions when I updated, so I just figured I'd reinstall the old version until I could get v23 sorted out. I got the same two errors with the old version as well.   Solutions I've found online (google - and this forum) which have proven unfruitful or non-applicable: 1. scratch disks 2. bad preferences 3. bad plugins   1. I do not believe it to be an error related to disk space available; my C drive has 130gb free and the previously used scratch disc is an empty 1TB SSD. I *cannot* get to the scratch disk settings via holding alt or alt+ctrl or whatever it is, because photoshop cannot even initialize to get to that point.   2. I have completely wiped preferences and attempted to re-start photoshop. This error does not even allow photoshop to finish building its prefs file/folder structure. There is *no* prefs file to delete.   3. See number two. Fresh install, no third party plugins installed (though I did have PPW panel plugin installed before I updated. I have not attempted to reinstall it since photoshop doesnt run at all)   I have reinstalled from scratch and rebooted the PC. The error persists.   Any ideas would be welcome, as would some form of contact from an actual Adobe customer support agent willing to work with me, rather than point me at the three solutions above. ... View more

The issue appears to be that the Distribute Spacing input is set to points at software startup, regardless of the user's selected unit of measure in preferences. Mine is set to inches and the box for Distribute Spacing in the Align panel says "0" with no denoted unit of measure. A little trial and error testing shows it's using points as the default. I can get the function back to correct by going into preferences and setting a different unit of measure, clicking OK, then going *back* into preferences and setting it back to the unit of measure I want to actually use. Then the box in Distribute Spacing will say "0 in" if I set to inches. Occasionally I'll notice it's fixed itself somehow, when I have multiple documents open. I haven't been able to determine what causes it to self-correct though. I suspect it may have something to do with opening a document(s) that were originally saved when the function was working correctly. ...but I really hate having to do that everytime I start Illustrator. ... View more

One of our first troubleshooting steps based on something our IT guy found/heard somewhere was to uninstall fontbase, but that did not fix the issue for us at the time. I suspect it has something to do with the fontbase associated files which were located in the Adobe CEP extensions folder before we deleted it. I don't believe that folder was deleted when we uninstalled fontbase. The folder has since been re-created by fontbase on my system, the folder is called "com.fontbase.activator" on my windows 10 workstation. Contained therein are the following items (bottom two are files, the others are folders): CSXS html js jsx META-INF mimetype package.json The folders contain various javascript, xml and html files. It was also noted that we did not experience any issues until we upgraded fontbase to the pro version, for what it might be worth to anyone. to mathewm, I an currently unable to reproduce any issues listed, including with object > path > offset path. ... View more

We have what at first glance what appears to be (temporary?) fix at my location, as we did not experience any of these issues before installing and upgrading Fontbase to the paid/pro version. Our IT upgraded our Fontbase to the latest (2.7.0) and delete a fontbase-related folder here: C:\Users\<username>\AppData\Roaming\Adobe\CEP\extensions I have confirmed on my workstation the issue is at least temporarily resolved. ... View more

It's been posted there, that's how I got the link to this forum post. Scaling object(s) is causing the associated bounding box to become a shape ('expanded object' appears on the screen afte… ... View more

We've now been seeing that a different user logged in with a 'fresh' account and preferences *on another user's workstation* does not experience the issue, whereas they do on their own workstations (Windows 10 enterprise, no dropbox, but Fontbase * Hotdoor CAD tools are installed and have been determined not to be source of the issue on our end): User A has this issue. User B has this issue. User C apparently does not, or has not reported experiencing the problem to this point. User A logs in to User B's machine (windows 10 sets up new account, fresh illustrator prefs, etc..) Issue does not manifest. User B logs in to User C's machine (same as above), issue does not manifest. Both User A and B continue to see the issue on their own workstations. ... View more