I just noticed ipfsOnPath was false on my own machine but true on the virtual machine... I changed it to true on my own machine but it made no difference...

I've tried the same install process (via chocolatey) on a virtual machine and it worked fine, so it's definitely something wrong on my machine only...

However I did notice that if you click Check for Updates during the 5 or so seconds that "IPFS is Starting" you do get the same crash.

Is there a way to see the full commandline to ipfs.exe that IPFS Desktop is trying to run? Then I can try run it manually... I don't even see ipfs.exe in task manager while it's in this state. I tried running this but it worked fine:

"C:\Users\jjv36\AppData\Local\Programs\IPFS Desktop\resources\app.asar.unpacked\node_modules\go-ipfs\go-ipfs\ipfs.exe" daemon --migrate --enable-gc --routing dhtclient

Here's my versions:

And here's my config (which I haven't changed):

{
	"ipfsConfig": {
		"type": "go",
		"path": "C:\\Users\\jjv36\\.ipfs",
		"flags": [
			"--migrate",
			"--enable-gc",
			"--routing",
			"dhtclient"
		],
		"keysize": 2048
	},
	"language": "en-US",
	"experiments": {
		"npmOnIpfs": false
	},
	"__internal__": {
		"migrations": {
			"version": "6.0.0"
		}
	},
	"openWebUIAtLaunch": false,
	"daemonConfigRevision": 1,
	"checkedCorsConfig": true,
	"window": {
		"width": 1441,
		"height": 901
	},
	"ipfsOnPath": false
}

We'll go over this in our next triage session, but any other details you could provide could be great - namely how you went about adding IPFS to path? What exactly did you do?

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

I had an error that said daemon wasn't running, so I tried adding ipfs to path for adding it to CLI, but I got this error.

If it's hard to fix, I suggest adding an in-gui method for launching daemon !

Specifications

• OS: win32
• IPFS Desktop Version: 0.9.7
• Electron Version: 6.0.12
• Chrome Version: 76.0.3809.146

Error

Error: spawn powershell.exe ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)

• OS: [e.g. macOS, Windows, Linux]
• Version of IPFS Desktop [e.g. 0.11.1]

Describe the bug

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

<!-- ATTACH LOGS

If possible:

1. From the "IPFS icon" menu in your menubar/system tray, go to Advanced → Open Logs Directory (for Linux users who do not have this menu, logs can be found in $HOME/.config/IPFS Desktop )
2. Find *.log files
3. Attach error.log and combined.log to this issue. -->

This was fixed in https://github.com/ipfs-shipyard/ipfs-desktop/pull/1729 and will be included in the next release. Thanks!

• OS: [e.g. macOS, Windows, Linux]
• Version of IPFS Desktop [e.g. 0.11.1]

Describe the bug

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

<!-- ATTACH LOGS

If possible:

1. From the "IPFS icon" menu in your menubar/system tray, go to Advanced → Open Logs Directory (for Linux users who do not have this menu, logs can be found in $HOME/.config/IPFS Desktop )
2. Find *.log files
3. Attach error.log and combined.log to this issue. -->

I'd specifically asked to use "Enable" since it's a little more accurate, and avoids visual repetition. If we' use "Enable" for each one, we might as well remove the word "Enable" altogether.

    "npmOnIpfs": "Enable npm on IPFS"

I'd suggest an icon-driven select menu like this one, positioned at bottom left next to the copyright line:

PRs for the other to menu items mentioned here: https://github.com/ipfs-shipyard/ipfs-desktop/pull/1739 and https://github.com/ipfs-shipyard/ipfs-desktop/pull/1740

@jessicaschilling broke that change out into a separate PR: https://github.com/ipfs-shipyard/ipfs-desktop/pull/1742

As requested by @jessicaschilling in https://github.com/ipfs-shipyard/ipfs-desktop/pull/1739#issuecomment-763893741

When IPFS Companion is enabled in Firefox, the website breaks:

Dropping quick notes:

• missing files.get (guess: a mismatch between HTTP client in Companion and old one in the app)
• multiaddr2URL conversion produces broken URL (guess: needs updating https://github.com/multiformats/js-multiaddr-to-uri)

window.ipfs is no more: https://github.com/ipfs-shipyard/ipfs-companion/issues/589#issuecomment-712356448

WebUI automatically detects locale based on request headers, but there is also UI for user to manually change locale.

(there is a bunch of complete translations at Transifex waiting to be used: https://www.transifex.com/ipfs/ipfs-share-files/)

Sorry for the delay! I have uninstalled ipfs-desktop via chocolatey and installed 0.13.2, 0.13.1, 0.13.0 versions manually and they all get stuck the same way. I don't have a IPFS_PATH environment variable set. I deleted the logs and then started the app again, and when it got stuck error.log was empty, and combined.log showed this:

2021-01-22T07:14:41.405Z info: [meta] logs can be found on C:\Users\jjv36\AppData\Roaming\IPFS Desktop
2021-01-22T07:14:42.037Z info: [web ui] window ready
2021-01-22T07:14:42.037Z info: [tray] starting
2021-01-22T07:14:42.134Z info: [tray] started
2021-01-22T07:14:42.134Z info: [ipfsd] start daemon STARTED

Pressing "Check for Updates" still crashes with that ctx.manualCheckForUpdates is not a function error as well.