Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this Windows 10 1809 ready? #86

Open
ImSpecial opened this issue Sep 26, 2018 · 19 comments

Comments

Projects
None yet
7 participants
@ImSpecial
Copy link

commented Sep 26, 2018

So the rumored 1809 release date is October 2nd, so it's just a week away from now, and I'm currently still using official Classic Shell 4.3.1, my understanding is that this version does not work with the new Windows 10, so I'll need to use this fork instead, is everything working okay on the newest Windows 10 1809 build? Where's the download link that people like myself should be downloading, and is there anything I need to do or make note of to carry over my current settings when I update Classic Shell to Open Shell?

@isshininu

This comment has been minimized.

Copy link

commented Sep 26, 2018

Classic Shell 4.3.1 works on 1809 so far.

@DrTeeth707

This comment has been minimized.

Copy link

commented Sep 27, 2018

Is this project still alive?

@XenHat

This comment has been minimized.

Copy link
Member

commented Sep 28, 2018

Is this project still alive?

Yes, definitely.
Progress depends entirely on the team members' availability. I am currently busy with other projects and other life matters.

@XenHat

This comment has been minimized.

Copy link
Member

commented Sep 28, 2018

Is this Windows 10 1809 ready?

Probably. We fixed the issue with the Insider Preview build, so there's no reason it wouldn't work.

@coddec

This comment has been minimized.

Copy link
Member

commented Sep 28, 2018

We are not dedicated full time Open-Shell developers.
We are from community as well just like you, so we need to take care of our lives just like others.

Thanks for asking though, it is still alive, confirmed.
Thanks for answering @XenHat long time ;) Sorry I'm currently busy with other matters too.

@DrTeeth707

This comment has been minimized.

Copy link

commented Sep 28, 2018

No disrespect was intended by my question. It is just when things go quiet, one does begin to wonder.

Cheers

DrT

@coddec

This comment has been minimized.

Copy link
Member

commented Sep 28, 2018

I do feel the same once a while, for other projects etc. etc.
Understood.
That's OK 👍

@ImSpecial

This comment has been minimized.

Copy link
Author

commented Sep 29, 2018

Wait so Classic Shell 4.3.1 works on 1809? And how does one upgrade to this fork if I decide to go that route, do I install over top Classic Shell or do I need to uninstall Classic Shell first?

@ge0rdi

This comment has been minimized.

Copy link
Member

commented Sep 29, 2018

Wait so Classic Shell 4.3.1 works on 1809?

Yes, it seems to be working well.
There was some issue with some RS5 preview builds in the past. But apparently MS did some fix and it works on final RS5 build (17763).

do I install over top Classic Shell or do I need to uninstall Classic Shell first?

It should be possible to install over ClassicShell.

Though there seems to be some issue with Windows Installer that it may not restart explorer correctly (this is not related to OpenShell only). And we don't have any automatic workaround for this currently.

So probably the safer option is to uninstall ClassicShell first. Settings will get migrated either way.

@DrTeeth707

This comment has been minimized.

Copy link

commented Sep 29, 2018

Hi,

Could you please confirm that the settings get transferred. The last I heard from one of the devs was that they did not and it was something that they were going to be working on. For that reason along I have not upgraded Classic Shell with Open Shell on my win 8.1 (x64) partition.

Cheers

DrT

@coddec

This comment has been minimized.

Copy link
Member

commented Sep 29, 2018

@DrTeeth707
Backup is always good ;)
If you are willing to take a chance.

  1. Backup classic shell settings (use export to xml option)
  2. Uninstall classic shell
  3. Install open-shell
  4. Import xml file to open-shell.

Though, I do not guarantee there's 0 chance of error.
If there's any, it won't kill your PC, the worst case is the open-shell can't work correctly, just reinstall classic-shell then. I haven't heard of any major issues though.
Take extra care if you have many skins installed for classic shell, I did hear that some custom skins can cause issue while using this way to migrate.

Good luck!


Edit: Ignore my comment, refer to @ge0rdi 's comment below.

Latest nightly build does import settings from previous ClassicShell installation.

It was added in this commit.

@ge0rdi

This comment has been minimized.

Copy link
Member

commented Sep 29, 2018

Latest nightly build does import settings from previous ClassicShell installation.

It was added in this commit.

@DrTeeth707

This comment has been minimized.

Copy link

commented Sep 29, 2018

Cheers. Will install that later today after backing up settings.
Many thanks for the info on the nightly.
Cheers
DrT

@ImSpecial

This comment has been minimized.

Copy link
Author

commented Sep 29, 2018

Just made the switch, seems everything went smooth, a big shout out to all you guys who are keeping this project alive, I was really dreading the Windows 10 update thinking this might break, but now I'm ready!

@DrTeeth707

This comment has been minimized.

Copy link

commented Sep 30, 2018

I backed up the settings and installed. I was pleasantly surprised to see that Classic Shell was uninstalled. Had to log out and then in again as the explorer process was borked (no task bar). I had a real struggle to get a shortcut for the settings onto the start menu as "pin to start" does not work. I had to copy the shortcut to the desktop and then drag it onto the start menu. That took as few goes as I have my control panel and admin tools to display as a menu and I had to avoid them or they opened and got in the way.
Cheers
DrT

@ImSpecial

This comment has been minimized.

Copy link
Author

commented Sep 30, 2018

"Had to log out and then in again as the explorer process was borked (no task bar)."

I had this too, scared the heck out of me thinking I borked Windows, my background wallpaper was black and no taskbar, I had to hit the power button to restart the PC... luckily it was all good when it rebooted. I'm thinking the uninstall/install process could be worked on to be a bit smoother.

@DrTeeth707

This comment has been minimized.

Copy link

commented Oct 1, 2018

No need, just need to make a restore point before installing beta programs. I was not worried about the explorer.exe issue as I have had it before. Explorer and also be restarted from the task manager.

It was the "pin to start" issue that flummoxed me.

Take care

DrT

@XenHat

This comment has been minimized.

Copy link
Member

commented Nov 28, 2018

Is this still an issue?

@dragnilar

This comment has been minimized.

Copy link

commented Dec 7, 2018

@XenHat I updated to 1809 a week ago and haven't found any problems myself. Not sure if you are waiting to hear back from @ImSpecial .

I noticed another problem (Classic Explorer doesn't seem to have a dark theme to match the new dark theme in File Explorer, unless I am just overlooking something). Do you want me or someone to make a Feature Request? You have #98 but it looks like that is for Windows 8, not 10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.