Windows 10 New 10 User with 3 issues

Rebop

Extraordinary Member
Joined
Apr 23, 2016
Messages
91
Hi folks,

New here and to Windows 10. After a week or two of learning and configuring, I have three problems and not finding much by searching or posting at Microsoft. Happy to break into separate threads if desired, but lets try the issues here:

1. New temp file with errors created every 7 minutes

Roughly every 7 minutes there is a new file created in Windows\Temp named something similar to cliEF78.tmp. The name changes slightly each time. The contents are always the same:

ERROR: A critical error occured while converting genuine authorization tickets on disk licenses.
Error code: 0x80041014.
ERROR: Failed! Error 0x!08X.

Now, Win 10 says it is activated and M'soft Office is activated, so what can be causing all these files and how do I stop it?

I have eliminated Adobe CC as a cause as well. Still happening.

2. I cannot create a recovery drive with System Files

Fails. Without system files work fine, bit I would like as much as possibe on the recovery. It also throws away half of the rescue drive. I took a 64GB and it is now 32 with no possibility of using the other 32 GB.

3. Registry searches crash regedit

Some others talking about this, but not going anywhere. My fav example is search for "dontrefresh". The search will not complete. When you cancel, it crashes regedit.

Any help here with any or all?

Thanks.

~Bob
 
Solution
What a great idea was ProcMon!

The file creator is clipup.exe. There is a service called clipsvc that I have tried disabling but the files still get created. So the exe is likely called by something else. But, likely it is phoning home trying to validate my license. This was a factory Lenovo install and shows as activated. So knowing this news, is there something to check / set / configure?

Thanks. Progress.

~Bob
Sort by date Sort by votes


SFC found nothing wrong. Run early on.

And these were all happening well before I installed any software as the first thing I do is configure options, create a custom view in events viewer, update the normal.dot with all my Word Macros, Install Outlook Stationary, etc. I do not believe it has anything to do with installed software.

Just going to run SFC again right now...

This time found some things and said to look at the log.My apologies for doubting. It is huge. Most seem related to running the test. This is the final summary after that:

2016-04-25 11:29:51, Info CSI 000052ae [SR] Verify complete
2016-04-25 11:29:51, Info CSI 000052af [SR] Repairing 1 components
2016-04-25 11:29:51, Info CSI 000052b0 [SR] Beginning Verify and Repair transaction
2016-04-25 11:29:51, Info CSI 000052b1 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-04-25 11:29:51, Info CSI 000052b2 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-04-25 11:29:51, Info CSI 000052b3@2016/4/25:18:29:51.794 Primitive installers committed for repair
2016-04-25 11:29:51, Info CSI 000052b4 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-04-25 11:29:51, Info CSI 000052b5 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-04-25 11:29:51, Info CSI 000052b6 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2016-04-25 11:29:51, Info CSI 000052b7 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-04-25 11:29:51, Info CSI 000052b8 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-04-25 11:29:51, Info CSI 000052b9 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-04-25 11:29:51, Info CSI 000052ba@2016/4/25:18:29:51.825 Primitive installers committed for repair
2016-04-25 11:29:51, Info CSI 000052bb [SR] Repair complete
2016-04-25 11:29:51, Info CSI 000052bc [SR] Committing transaction
2016-04-25 11:29:51, Info CSI 000052bd Creating NT transaction (seq 2), objectname [6]"(null)"
2016-04-25 11:29:51, Info CSI 000052be Created NT transaction (seq 2) result 0x00000000, handle @0xdb4
2016-04-25 11:29:51, Info CSI 000052bf@2016/4/25:18:29:51.841 Beginning NT transaction commit...
2016-04-25 11:29:51, Info CSI 000052c0@2016/4/25:18:29:51.856 CSI perf trace:
CSIPERF:TXCOMMIT;20005
2016-04-25 11:29:51, Info CSI 000052c1 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

What seems most interesting and seems like it was unable to repair is the opencl.dll.

Thoughts?

~Bob

Must do some real work today. Will try to get to more questions.
 
Upvote 0 Downvote

Why would it matter who paid for this? My company. Ordered through CDW. Not sure how that could make a difference....

I try not to bother IT if I do not have to. And this computer, being the first Win 10 in the (large) company is not officially supported. SO I will avaoid that. Especially since there may be a new clue in the one aboive and the other two issues are had by many who are not on domains at all.

Let's put a link or two here for those:

http://answers.microsoft.com/en-us/...2/a70e0cb9-46a3-4fac-a103-4fee65d19eb8?page=7

http://answers.microsoft.com/en-us/.../be343c15-b2bf-4c62-ad10-e6b79dc29be9?page=27

Those lead to the end of the threads. You might check the beginnings.

I can likely create a local login. not sure I have time or it is necessary - at least yet. I have ADMIN rights, of course.

Not sure what vagueness you are referring to? Its company owned. I have been on the domain for 12 years on several computers. Vagueness? I also do not believe this has anything to do with the issues.

~Bob
 
Upvote 0 Downvote
Rebop said:
Why would it matter who paid for this? My company. Ordered through CDW. Not sure how that could make a difference....



~Bob
Click to expand...


Just read your entire first message. Thanks, but I think waaaay off base. This computer was put on the domain by IT. It is not supported by them. I do not believe ANY of these issues involve domain at all. I do not need to be told about case law. I am trying to evaluate the issues I find in Win 10 both as to how it may affect me and the company once it IS (if ever) supported by IT and how it affects the applications I product manage for my customers who are already on IT.

Thanks for your interest, but it has nothing to do with 2 of the issues, and while I will allow a chance that maybe something "trying" to push through group policy might have something to do with the third, I think it is remote.

Not having the time to reply is not vagueness, either.

And who owns that machine should not be a root cause of hundreds of temp files created by clipup.exe daily, imho.

But thanks. Seriously.

~Bob
 
Upvote 0 Downvote
The opencl.dll error is not related. Has to do with a video driver issue. Not sure why that pops up now, but the "cl" part had given me hope on the temp files.
 
Upvote 0 Downvote
Yes, openCL is related to non directX graphics support. Being on a domain would not causes the clipup.exe issue. I did dump the strings from this process and it does look like it has to do somewhat with key activation, windows phone and windows store authenticity checking. Did you run procmon with the filter I suggested?
 
Upvote 0 Downvote
Is it possible the problem started way back in January, with the a failed attempt to load a game add-on, or ?
 
Upvote 0 Downvote
Hi

I haven't read though all of this so this may be a dumb question but have you tried turning off Clipup.exe in Services?
If what you are seeing it the legitimate windows process it should show in the Services list.

I don't have it active on my computer at all, so I can't check to see if I can turn it off on mine.

I found the file at this address....

C:\Windows\WinSxS\amd64_microsoft-client-li..m-service-migration_31bf3856ad364e35_10.0.10586.0_none_23891e90c02e780f\Clipup.exe

You could try renaming it to StopClipup.exe and see it removing it would cause and problems, it doesn't seem to be essential.
If that doesn't work all you have to do it change it back.

Mike
 
Upvote 0 Downvote
 
Upvote 0 Downvote

I did. That's how I determined it was clipup as the cuilprit. However., I may not have created the most elegant filter nor found all the results you might be looking for so happy for more direction in that regard.

~Bob
 
Upvote 0 Downvote

Thanks Mike. I did mention this.

I have renamed the exe and it continues. I have stopped the only related service and it continues. So....

Only good news is that over at my topic on this at Microsoft, someone finally posted they have the exact same issue. So at least not only me

Interesting one, eh?

~Bob
 
Upvote 0 Downvote

Thanks again. The news today is another user finally reported they have the identical issue at my topic at the MS support site. So once again, I think this issue is not domain related, though I will keep that as an open possibility.

We are a big company. I am THE unique power user. I was the first with Win 7 long before it was supported for the company. And I am on the domain for email and files transfers, nightly builds, etc without having to use another computer and transfer files to this one back and forth. It also tells me a lot about the issues the company may encounter in deploying 10 when and if as well as issues my customers may have using my software products on their win 10 machines.

3 issues is not horrible. I do consider each of them serious. My users will never do a registry search. They may never look in their temp directories. But I want to know root cause of these issues before I report on the viability of 10 for enterprise as well as 10 for my products.,

~Bob
 
Upvote 0 Downvote
I guess I should ask, is this Windows 10 Enterprise or Pro and if it's enterprise can you run slmgr /dlv and post
 
Upvote 0 Downvote
Hi Bob,
Thanks for your reply back in Post #52. That certainly provides at least me with more information on the network side of it, size of your company, Win10 version, etc. and your role in testing & deployment. I worked closely with app developers in many of my IT positions, and you guys are invaluable as long as we keep a dialog open on what you are doing and your goals. Internally, developers are considered valued customers in most IT shops--however, as you may be aware, they can have abrasive personalities, and that's true of some us IT types too. Working together and communication makes things run much smoother for both. At one company, I had difficulty understanding why my boss gave so much latitude to one of our software developers, but later I discovered that he was employee #3 in the company and had developed most of the early product architecture of all our product lines. He was extremely eccentric and legendarily difficult to work with. When I found this out, and went to have an in-person talk with him; he only came into the office a few days a year as he did 99% of his work from his home office over the network. He was a significant bandwidth user on our corporate network too. After speaking with him, we developed a close relationship after that, and I made it Job #1 to help him with his unusual requirements. Things went so much more smoothly for me especially, and I learned a ton from him. That's why it's important to keep the dialog open between developers and IT people. His work produced millions upon millions in revenue for our company over the years. It sounds like you are in a similar role in your Company. I might suggest that someone in your IT department can find the value in your work and you can work together to solve any other Win10 deployment problems that crop up.

Best of luck,
<<<BBJ>>>
 
Upvote 0 Downvote
OK. Captured the event and watched the temp being created. Can I email you this file rather than post it here?

~Bob
 
Upvote 0 Downvote
Looks like you have two svchost containers accessing clipup. I would run the command tasklist /svc and look at PID 3620 and 376 and see what services are running in those containers to help narrow down which one is calling clipup.
 
Upvote 0 Downvote
376 is an audio endpoint builder. Likely not it.

I have no 3620. Will check a few times....

Seem to be about 11 svchost running, but none 3670.

Let me know what else to try and I will in the morning.

Thanks.

~Bob
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Solved
Windows 7 Intermittent USB 3 Issues Causing Boot Problems and Mouse Malfunction on Windows
2 3
Replies
59
Views
8K
seekermeister
M
  • Solved
Windows 7 unreal tournament 3 issues
Replies
4
Views
8K
Mirrorboy
M
D
  • Solved
Windows 7 fallout 3 issues
Replies
16
Views
15K
kappox
K