Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

windows 10 and cps 12.3.2

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

13 Posts

10 Users

0 Reactions

101 Views

RSS

lic08

(@lic08)

Posts: 286

Reputable Member

Topic starter

i'm installed cps fat client on windows 10 v 1809. i was able to run cps and get the login prompt. After the prompt, cps does not load. I have no problem with windows 7, but windows 10 is giving me a hard time. Any suggestion? thanks.

Posted : January 9, 2019 8:52 am

dmcintire

(@dmcintire)

Posts: 48

Trusted Member

Apparently there is an incompatibility with Centricity and a specific windows update(Microsoft Windows 10 update 1809). Uninstall the offending update and see if it works. Here is a link to the post about the problem.

https://digital.gehealthcare.com/s/group/0F934000000D12j/centricity-practice-solution?s1oid=00D80000000PUBS&s1nid=0DB34000000Ce3O&emkind=chatterCommentNotification&s1uid=0053400000ALWJz&emtm=1546976631633&fromEmail=1&s1ext=0

Posted : January 9, 2019 9:01 am

Sarahgutierrez

(@sarahgutierrez)

Posts: 13

Eminent Member

Same thing happened to us a couple days ago with CPS 12.2 when loading a new computer. Going back a window version works

Posted : January 9, 2019 9:05 am

virtualHITman

(@virtualhitman)

Posts: 319

Reputable Member

Our VAR notified us of the issue at the end of November. This is a big problem for folks running CPS on a fat client. All new computers that Dell ships have build 1809 or later so there is no way to roll back to a previous version of Windows. The only way we can get Centricity to run is to set the user to run Centricity as a thin client. I am hoping Virence addresses this issue very soon. Surprised there hasn't been more noise about this in the forums.

Greg

Posted : January 9, 2019 9:50 am

tnc

(@tnc)

Posts: 517

Honorable Member

We have been rolling out Windows 10 LTSB mainly due to this specific fear. I felt like I was taking a chance with the version especially since I never got answers to my "Am I allowed to do this" question from Virence. At least for now I feel a bit vindicated but still fear some other unknown. I wish there was better communication with all of this.

I just wonder if there is a recommended developer path that Microsoft lays out so that 3rd party apps will survive these updates-and someone or some people ignored them.

Mike Zavolas
Tallahassee Neurological Clinic

Posted : January 10, 2019 1:41 am

bjakovcic

(@bjakovcic)

Posts: 8

Active Member

Has there been any update on an actual resolution for this issue? Anyone hear anything?

Posted : January 14, 2019 3:49 am

virtualHITman

(@virtualhitman)

Posts: 319

Reputable Member

Here is what I received from our VAR this morning. Looks like Microsoft is aware of the issue and will have a fix in February timeframe.

ISSUE: KM 000043798 - CPS - Client - Windows 10 Machines with Build 1809 will not run CPS - !!CRITICAL!!

ACTION: Greg, I inquired as to this issue with Virence and received the following information: "The Build 1809 screwed up an approved C# programming function, MSFT has acknowledged it was a regression and will be re-releasing 1809 in Feb (probably as a different build ##) and they are indicating that a fix for this issue will be included." Please let me know if you have any more questions about this.

Posted : January 14, 2019 3:55 am

evanbjones

(@evanbjones)

Posts: 1

New Member

Could you please copy and paste whatever is in what you linked? I don't seem to have access to it. Very curious about this problem and if there is a workaround available yet.

Thanks!

Posted : January 28, 2019 2:08 pm

Henwai

(@henwai)

Posts: 1

New Member

We are experiencing the same situation with our test environment with CPS 12.2. Does the re-release 1809 work for anybody?

Thanks!

Posted : February 28, 2019 3:50 am

lic08

(@lic08)

Posts: 286

Reputable Member

Topic starter

anyone know if it's fixed yet?

Posted : March 5, 2019 5:57 am

virtualHITman

(@virtualhitman)

Posts: 319

Reputable Member

We continue to have issues with Windows 10 forcing the 1809 build on users and then we have to perform a rollback to the previous version of Windows. I spoke to our Value Added Reseller again this week about the problems this is causing and the fact that Virence keeps saying a fix will be released in the next month. As of this week, I was told that Virence sat down with Microsoft and has received "official" word that a fix may be out as early as the end of March, but more likely April. I've heard all of this before, so I remain skeptical until I see an actual fix.

Virence has access to pre-release builds of Windows updates before they are released to the general public. It would not have been difficult to see that build 1809 would not work with Centricity. So...what does that tell you about Virence's regression testing protocols? Uhhh...that their non-existent? Hope Virence learns something from this. This isn't the first time this has been brought to their attention.

Posted : March 15, 2019 12:16 am

rtisovec

(@rtisovec)

Posts: 1

New Member

It appears that the latest Microsoft update to 1809, termed "Cumulative update for Windows 10 1809" Has fixed this issue.

April 2, 2019—KB4490481 (OS Build 17763.404)

I have been at least able to launch CPS remotely, have not had a chance to use in the office as of yet, but it seems (at least as long as they don't screw it up with pending 1903 update) that CPS now works with Windows 10.

Link to what is included in this update. I don't know that this specific issue was listed.

https://support.microsoft.com/en-us/help/4490481/windows-10-update-kb4490481

Posted : April 2, 2019 6:41 am

DavidShower

(@davidshower)

Posts: 1255

Noble Member

Didn't fix it for me - laptop with Centricity client connecting to a VirtualBox 2012R2 VM running CPS.

Posted : April 2, 2019 11:37 am

24 Forums
9,940 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed