Windows 10: Many Creators Upgrade Problems?

lightwortks 14.0.0.0 stopped working
start craft 2 no longer loads
fonts in royal TS v4 are corrupted.

other than that...

 

My other two machines (two desktops) were a clean upgrade.

I'll try the laptop again in the morning.

Chris

 

I updated 2 notebooks, Chrome works with no issues on both.

 

I have the CU with no problems. The upgrade went very smoothly for me ...

 

Same here , not an issue one. Three laptops and two desktops all of various configurations from Gaming to purely work/office.

 

All is now well with Chrome after a re-install of CU.

Chris

 

My boot time across three W10 instances (2 different computers, 3 different boot hard drives) has increased ridiculously.


Also seems there is a heck of a lot more disk thrashing than ever starting programs....

 

System specs would help give us an idea of what's happening.

 

Sys 1

Asus mobo
i7
16 gig RAM
boot drive 1 WDC 32M cache
boot drive 2 (used in an audio environment and not typically networked) Seagate 64M cache


Sys 2

Gigabyte mobo
8 gig RAM
boot drive WDC 16M cache



Literally no changes other than installation of Creators Update.


Thx,


Greg

 

Thanks. The specs just tells us what you're running and give an idea as to performance of system. That said, all we have to go by is you saying boot times have increased ridiculously before the update. But slow compared to what? How do you define "ridiculously"? How slow is that?

Anyway boot times can be affected by a myriad of things so It's hard to say what's causing slower times. Just FYI, I've not noticed any increased times on any of my updated PC's. On the other hand I've not measured them. They just seem the same to me.

Also bear in mind, you have traditional hard drives that'll boot Windows slower than any SSD drive. Point being when comparing your new boot times to on another make sure you're comparing HDD to HDD, not HDD to SSD!

 

Thx for your input.


However please note the ONLY change that has been made (x3) has been the update.

And "ridiculous" can be quantified by 2-3 times longer each system takes to fully boot and become usable. As in COMPLETELY noticeable and not needing an actual time hack to measure the difference.

I'm quite aware of SSD vs HDD - however that isn't the issue here at all. I've built studio quality systems for years and fully understand the building, operation, updating and usage of high end systems.

There is an issue with this update. Plain and simple. And yes, I understand many have had zero problems. However my experience has been completely different.

 

I just finished upgrading two desktops and a laptop. Not a single issue and all running great. Fast as before.

 

if someone wants to come down on microsoft it is their right.

 

We don't know what your qualifications are and assume nothing. This provides for better help in assuring we aren't talking over people's head who may not be so knowledgeable. Now that you stated your qualifications we can move from there.

With that I would check task manager to see what's running that maybe shouldn't. Did you disable tasks or remove stuff that would be reset during the upgrade? Perhaps this is a reason for your slowdowns?

While I'm never one to assume because I have no issues, no one else does; I'm also of the mindset that just because some have issues doesn't mean the entire process is broken. There are simply too many PC configurations for any upgrade to not break something. It happens.

What you look at though in this case are the numbers.... and the vast majority have not experienced the issue you post. It doesn't mean you don't have issues, but it does lend credence to the notion that the upgrade isn't as problematic as you simply state.

That said, no doubt you feel there's an issue with your upgrade... the question is what's causing it? At this point I have no idea other that what I said earlier - check to see if any settings you'd previously tweaked, removed, or disabled, got reset as major upgrades such as this do tend to reset stuff.

Good luck.

 

I'm now seeing even more problems - there is a post here about chkdsk not working Chkdsk not working?

Why didn't MS software engineering process discover and fix such a basic error?