Problem with System Metrics SM_CXSIZEFRAME + SM_CXPADDEDBORDER in Windows 10 Preview (Build 10041)

Maybe this forum is the wrong place to ask something about Windows 10 Preview, but I did not find a dedicated place to report
programming problems as opposed to user problems:
I program/maintain a 32-bit desktop (WIN32 API) application and try it now on Windows 10 Preview build 10041. I calculate the size of a window border with the help of the GetSystemMetrics function, using the constants SM_CXSIZEFRAME and SM_CXPADDEDBORDER.
Originally, I only used SM_CXSIZEFRAME. This returned 4 pixels instead of the expected 8 pixels that I got on all previous windows versions up to Windows 8.1. Then I learned that already since Windows Vista one is expected to add the value of SM_CXPADDEDBORDER
to get the full border size. (SM_CXSIZEFRAME alone only continued to work on Vista and beyond thanks to a little compatibility hack by Microsoft, with SM_CXSIZEFRAME still returning the full border size and SM_CXPADDEDBORDER returning
yet 0, at least for 32-bit programs like mine.)
Assuming that Microsoft finally switched off that compatibility measure on Windows 10 I query and add SM_CXPADDEDBORDER now as well. Unfortunately this does not solve my problem, as that system metric returns 0.
Just to be on the sure side, I declared my program to support Windows 10 by using an embedded manifest and using the corresponding <compatibility> / <supportedOS> line with the Windows 10 GUID - this did not help either.
As querying and adding those two system metric values is rather trivial (no need to include code in this question, I think), I don't have the slightest idea what
I could do wrong here, this looks like Preview bug affecting 32-bit programs to me...

I regret to inform you, that you have to live with this error for ever. Microsoft won't fix it... we reported an error of the Windows Error Reporting system (exists since Windows 8) and provided a reproduction (an application with one printed page of code,
so very small and easy). It has never been fixed. 3 developers at Microsoft are involved and they confirmed, that it's a bug ... but... no chance. It's a strange company... I don't know what they mean with "we listen to our customers".
PS: ja, nöd grad hilfriich mini Kommentär, aber die Type triibed eim eifach in Wahnsinn!! ... schinbar nöd nur öschtlich vo Bade, sondern au weschtlich
Rudolf

Similar Messages

7.1 | Problems with System-metrics templates generation

Hi experts.
I've got a few questions.
At first im facing a problem after reinstall a DAA on automatic conifguration:
System-metrics templates generation failed (cause :Unexpected error occurs in task execution. (detail: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 1a, 1b, 56(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 1a, 1b, 56(:main:, row:1, col:3)), state:4)
I found note 1669789 where i have to check my LM-Service Level on Solman 7.1.
--> Where can i find it? In SLD i cannot see it.
Then i read that i have to apply the LM-Service patch with JSPM
--> Isnt JSPM obsolete? I think i have to use SUM? So i thought i have to do a big SPS-Update otherwise?
The other stuff in the note doesnt help. If my LM-Service is okay, do you have other ideas?
Thank you for your help!

I found note 1669789 where i have to check my LM-Service Level on Solman 7.1.
--> Where can i find it? In SLD i cannot see it.
Goto systeminfo from http://host:50000 to check LMservice
--> Isnt JSPM obsolete? I think i have to use SUM? So i thought i have to do a big SPS-Update otherwise?
LM-service should be updated from SUM and then you have to re-run java upgrader.
1st enable maintenance mode from agent admin.
Deploy SCA from SUM
Disable maintenance mode from agent admin.
Run java upgrader from solman_setup
Divyanshu

Problems with System Update 3.14.0019 after installation SP2

Have you encountered problems with System Update 3.14.0019 after installation SP2 for Windows Vista?
After this upgrade I view this error: "An error occurred while gathering user information."
Thanks for the help

A known issue. It wasn't supposed to be supported until SP2 is RTM. However, look at the stickied post in the forum for some bad news about SU.
x61s

Problem with two monitors while using Photoshop, windows move from 2nd screen to 1st screen.

Problem with two monitors while using Photoshop, windows move from 2nd screen to 1st screen.
I saved a new workspace and it did not help.
No problem before I went to Maverick.

I found the fix, go to System Preferences and open Mission Control and uncheck the box to keep monitors as they were (When switching to an application...........)

Solution Center problem with HP Office Jet J4550 and windows 7 (64bit)

Hello All,
I have a problem. I have the Solution Center and a HP Office Jet J4550 and windows 7 (64bit). When ever I open the solution center, the solution center says " HP office jet J4550 series disconnected" When I open HP document manager, I can access the printer. Additionally, when I run the HP Print Diagnostic Utility 4.0, it sees the printer, no issues. I can print test pages. No issues. I downloaded the latest driver from the HP site (OJJ4500_Full_13, 299,359KB) Your insight is appreciated.
Thank you
Roy B

I have a similar problem with the J4580 and my new Windows 7 64-bit laptop. HP Solution Center says that the printer is disconnected. Furthermore, it can print some documents (short ones), but it was unable to print a 1-page 5MB pdf file. The printer truncated the page after printing just the top 10%. The printer is OK with my wife's Windows 7 32-bit laptop.
I've seen many other people complain about similar problems in this and other forums. Apparently the driver for J4500 printers is not compatible with Windows 7 64-bit. Can HP please provide an updated driver or patch?

When installed JDK but I have problem with System vars may install bundle

When installed JDK but I have problem with System vars may install bundle [netbeans&JDK] WITHOUT UNISTALLING initial JDK or needed uninstall first ?

With the word 'automatically', yes you do need pulseaudio. I'm sure you could cook up some udev or related rule to do that in Alsa, but pulseaudio would be easier.

Window 10 build 10041 does not work with Intel 82579V Gigabit Ethernet on ASUS motherboard

I originally posted this question here:
answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/window-10-build-10041-does-not-work-with-intel/6729892f-83aa-4822-b20a-ea84f4fd06c7
and was asked to post it on this forum...
I updated a computer I have which is a quad core i7 that I built and includes an ASUS motherboard with Intel 82579V Gigabit Ethernet built in. Windows 10 preview 9926 worked fine with this network adapter. Window 10 build 10041 does not, and I have tried
it twice so far. I even went as far as buying a Thunderbolt-Gigabit Ethernet Adapter (Broadcom, sold by Apple)... and while it installed the driver automatically, it did not work either. Each time you try to view the properties of either of them, it locks
up or give an error. In fact, doing much of anything with the Intel adapter icon assures you of not being able to do a clean reboot... have to kill power. I have finally gone back the previous version 9926, which has its issues but no where near as bad
as not having any network connectivity! Does anyone have this issue and a workaround?
Note, there are two images on the windows 10 preview forum that I posted this question on. I could not post the full link as I was getting a message here that links and graphics are not allowed.

Thanks Roger, I posted the following yesterday in the other thread (thinking it was this thread - confusing after they moved it here)... It may be that the new driver fixes the issue that 10041 has with it, but I have not tried that yet. If I do I will update
this... Thanks!
I have more information about this, which basically exonerates any issue with the Intel 82579V Gigabit Ethernet hardware or software. I have 3 computers with Windows 10 preview so I have multiple angles to see issues from. With this I have found a culprit
(but I suspect not just the only culprit) in this above mentioned problem...
10041 build combined with installing (or attempting to install) CISCO VPN Windows 7 64bit 5.0.07.0440-k9 client causes the issue mentioned above. I confirmed this on a completely different machine with a totally different Ethernet adapter. First machine
is an ASUS motherboard in a tower system I built, with the Intel 82579V Gigabit Ethernet hardware built in. Second machine is a Gateway Laptop from 2008 which has a Marvell Yukon 88E8057 PCI-E Gigabit adapter built in. Build 10041 will work fine with my 2008
laptop, including the MS VPN client (which I have tested). However, if you attempt to install or even uninstall the Cisco client you will have to do a recovery to a restore point (as I have done twice) in order to get your network working again. Installing
or attempting to install (because it never even does install properly and times out), CISCO VPN client will render your entire network unusable. Going back to a restore point saved me and I am still running 10041 but I can't use CISCO VPN client any longer.
I could with build 9926, including on all 3 machines. I now have 9926 on two machines and 10041 on only the 2008 laptop.
Hopefully this above information helps someone resolve the issue. I will also mention, even though my network is working on the 2008 laptop, I still can't go into the Control Panel\Network and Internet\Network Connections and right mouse click on the Marvell
Yukon 88E8057 PCI-E Gigabit adapter icon. I get an error when clicking on Properties menu popup : "An unexpected error has occurred". So something is still up with my network adapter driver or windows software, but it could be a side effect of all
that has happened with the Cisco software install attempts under 10041.
Another note: CISCO Anyconnect also has the issue.

Windows 10 build 10041 32bit crashed hp envy x2 tablet/notebook black screen

Hello all,
Upgraded from Win 8 to 8.1 the 10 preview build 10041 (32bit), online upgrade (as machine will not boot from usb), worked well for one day. Then I changed update option from 'only notify me of available updates' to 'automatically install updates for windows' or somesuch.
For two days, can only get black screen using all combinations of shift/ctrl/fn/windows key with f2/f8/f9/f10/f11 keys.
Holding the power button down for brief or long period. With mains power lead inserted or not. With tablet connected to base or not. Ran down the battery, no change.
I suspect the problem is due to the Win 10 O/S is perceived as an alien O/S by the system. Prior to updating to Win 10, I was unable to boot from usb or access legacy boot.
My machine:
HP envy x2 pc
product number c8c42pa#abg
serial number 4cn2480dgk
Bios was updated from f12 to f13.
Thanks in advance, AA

Hi,
Did you read the following Agreement before installing Windows 10 preview ?
https://insider.windows.com/Home/TermsOfUse
Specially section 4.
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Windows 10 Build 10041 start menu not working

I have installed the Windows 10 Build 10041 update yesterday. But since then I can’t leave my computer till it sleep automatically. Otherwise my computer will complete died and I need to press the power bottom to restart Windows.
But at that time, the Wndows start menu is still working.
However, this morning I find that my computer start menu is not working, and the search bar, Windows key, notice board icon at right side and internet icon is also not working. I have use the control panel to check the problem but
it could not find any faults.

Hi,
What's the type of your current user account? Built-in Administrator account or others?
Generally speaking, you can try to create a new user account to fix this problem. If no use, please try to use system restore to revert your system to a former normal time point for test.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Enabled Hyper-V causes "System thread exception not handled" BSOD in builds 10041 and 10049

I had a Windows 10 TP build 9926 installation with Visual Studio 2013 Community Edition installed, when build 10041 was released Windows Update tried to install it but after restart it got BSOD with "System thread exception not handled" text and
reverted back to 9926 with error code 0xC1900101-0x40017. I tried update from ISO, got the same BSOD. Tried clean installation, it worked.
I decided to install software and restart the system after each installation and discovered that installing Visual Studio 2015 CTP6 caused BSOD after restart if and only if emulators were included. Installation of Visual Studio 2015 CTP6 without emulators
and then installation of Tools for Windows 10 also caused BSOD with "System thread exception not handled" error after restart.
So I thought that it was Hyper-V related and disabled hardware virtualisation in BIOS settings. It worked, system successfully booted, but, of course, Tools for Windows 10 setup showed up and told me about fail in UAP for Windows Phone package.
So, my hardware is Gigabyte GA-A75N-USB3 motherboard with AMD A8-3870 APU with integrated graphics, Intel SSDSA2CW080G3 80GB SSD and 8 GB RAM.
Steps to reproduce are to enable "Virtualisation" item in BIOS settings, install Windows 10 Technology Preview Build 10041, install Visual Studio 2015 CTP6, install Visual Studio Tools for Windows 10 Preview, restart the system and
see blue screen with white text of description of "System thread exception not handled" error.

Same issue, MSI A75MA-G55 AMD Fusion Socket FM1 with A8-3850 APU, 16GB RAM. Hyper-V worked in 9926, but broke in 10041 and remains broken in 10049. I have found that if you get in this BSOD loop, you can boot to Safe Mode and Un-install Hyper-V
to recover. 10041 was an update to 9926, and 10049 was a clean install.

Dell Bluetooth 365 not detected in Windows 10 Technical Preview (Builds 10041 and 10049)

When I installed Windows 10 build 10041 on my 2009 Dell Inspiron 1545 laptop my Bluetooth 365 stopped working. On investigation I saw that Bluetooth had disappeared from Device Manager completely, but no yellow '!' was apparent anywhere. When I checked the BIOS the Bluetooth card was present. I researched the issue for a couple of hours and realised that Dell did not have a Bluetooth 365 driver for anything later than Windows 7. (That Windows 7 driver had worked in Win 8/Win 8.1). I discovered that the card is made by Broadcomm and is also used by Lenovo in some of its laptops. I downloaded the following driver from Lenovo's support site and installed it. When prompted, click the 'update software' button, and a further installation will run. If you wish, have Device Manager open and you will see the drivers and devices install.
support.lenovo.com/.../ds031759
It worked perfectly and my Bluetooth card was detected and configured and now all my Bluetooth devices work with Windows 10.
The Dell 1545 with Bluetooth is a great workhorse PC and it would have been a shame if it could not have been used with Windows 10. I hope it is not a sign of forced obsolescence by Dell, and that they will release Win 10 drivers for this venerable old laptop. It is a shame to have to go to a competitor for a driver. Judging by my web research there are many of this model still in everyday use. I trust this will be of use to other users.

There is a universal Broadcom Bluetooth Update which would cover this also:
http://www.broadcom.com/support/bluetooth/update.php

Problems With System Configuration

System Configuration is altered and not repairable. Selective startup is persistent. Normal startup is selected, but the Apply button is greyed out, inaccessible, and system always remains in Selective startup. As a result, Current User profile is probably
corrupted. Windows Store will not install (services are corrupt, SFC and DISM did not work). Outlook profile was deleted, needed to be reinstalled, and can not receive mail. Excel math engine totals values higher than actual amounts. IE automatically signs
into all Microsoft accounts (reset to default settings worked for a log on, but automatic sign in resumed afterwards).
Are there any solutions?
Office diagnostics produced the following report.
Diagnostic Results
None of the Microsoft Office Diagnostics found any problems.
More resources
Setup Diagnostic — File corruption or altered file
The Setup Diagnostic repaired problems with your installation of Microsoft Office. Your Microsoft Office programs should now function correctly.
If your Microsoft Office programs continue to crash, the source of the problem may be a hardware failure or hardware configuration problem. Review the results of the Disk and Memory Diagnostics to determine if a hardware failure is affecting your installation
of the 2007 Office release.
More resources
Setup Diagnostic — Missing media
The Setup Diagnostic was not completed because a valid source was not found. Either the local installation source is missing, or the original source that was used to install Microsoft Office is not available to the repair process. You may need to provide
the original source to allow this diagnostic to run successfully. Valid sources for the 2007 Office release include the following:
Your 2007 Office release installation CD
An installation disk or repair CD provided by the vendor of your computer
A connection to a network installation of the 2007 Office release
After you obtain access to a valid source, run Office Diagnostics again.
More resources
Disk Diagnostic — Failure of hard disk predicted
The Self-Monitoring, Analysis, and Reporting Technology (SMART) feature of your hard disk has found errors that may indicate that the hard disk is likely to fail. SMART is a feature that some disk drive manufacturers provide to give users advance notice
of potential hard disk failure. Instability in your Microsoft Office programs may be the result of these hard disk drive errors.
Note This result can indicate a severe problem, but some hard disks may not accurately report their results.
We recommend that you do the following:
1.Back up your important data immediately.
2.Check the results of other diagnostics, and follow the instructions for resolving any issues that the other diagnostics have reported. After you resolve those issues, run Microsoft Office Diagnostics again to see if this Disk Diagnostic issue is resolved.
3.If you continue to get this result, contact someone, such as the vendor of your computer or hard disk.
More resources
Disk Diagnostic — Errors in system event log
The Disk Diagnostic found evidence of hardware errors. Instability in your Microsoft Office programs may be the result of these hardware errors.
This result occurs if one of the following has happened recently:
The Self-Monitoring, Analysis, and Reporting Technology (SMART) feature of your hard disk has found errors. SMART is a feature that some disk drive manufacturers provide to give users advance notice of potential hard disk failure.
Microsoft Office Diagnostics has found blocked-out (failed) sectors on your hard disk.
Microsoft Office has had trouble accessing files from the hard disk; it needs these files to function properly.
We recommend that you do the following:
1.Check the results of other diagnostics, and follow the instructions for resolving any issues that the diagnostics have reported. After you resolve those issues, run Microsoft Office Diagnostics again to see if this Disk Diagnostic issue is resolved.
2.If you continue to get this result, contact someone, such as the vendor of your computer or hard disk.
More resources
Memory Diagnostic — RAM failure
The Memory Diagnostic found evidence of failure in the random access memory (RAM).
We recommend that you do the following:
1.Check the results of other diagnostics, and follow the instructions for resolving any issues that the diagnostics have reported. After you resolve those issues, run Microsoft Office Diagnostics again to see if this Memory Diagnostic issue is resolved.
2.If you continue to get this result, do either of the following:
Run a Microsoft Windows memory diagnostic. For more information, see the following:
Windows Vista How do I know if my computer has a memory problem?
Microsoft Windows XP Windows Memory Diagnostic
Contact someone, such as the vendor of your computer or RAM.
More resources
Memory Diagnostic — User is not an administrator
The Memory Diagnostic was unable to run because you do not have administrative rights on this computer. To successfully run the Memory Diagnostic, someone with administrative rights must log on to this computer and run Microsoft Office Diagnostics.
More resources
Update Diagnostic — Installation is out of date
The Update Diagnostic determined that your installation of Microsoft Office does not have the latest service packs installed. Installing service packs improves stability. We recommend that you visit Downloads on Microsoft Office Online, and then, under Office
Update, click Check for Updates.
More resources
Compatibility Diagnostic — Conflicting versions of Outlook found
The Compatibility Diagnostic identified conflicting versions of Microsoft Office Outlook. To remove the version of Outlook from your computer that you do not want, do the following:
Microsoft Windows Vista
1.Click the Start button, and then click Control Panel.
2.Click Uninstall a program.
Note In Classic view, double-click Programs and Features.
3.Select the version of Outlook that you do not want, and then click Uninstall.
Microsoft Windows XP
1.Click Start, and then click Control Panel.
2.Double-click Add or Remove Programs.
3.Select the version of Outlook that you do not want, and then click Remove.
More resources

Check disk and memory diagnostics found no errors.
SFC and DISM listed errors when performed in diagnostic start up. Commands changed from previous attempts. Before SFC and DISM only had to be entered as SFC and DISM. Presently, additional commands are required.
Log Name:      Microsoft-Windows-MemoryDiagnostics-Results/Debug
Source:        Microsoft-Windows-MemoryDiagnostics-Results
Date:          8/21/2014 12:51:09 PM
Event ID:      2001
Task Category: None
Level:         Information
Keywords:
User:          SYSTEM
Computer:      TAS
Description:
Windows Memory Diagnostic results
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5F92BC59-248F-4111-86A9-E393E12C6139}" />
    <EventID>2001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-08-21T16:51:09.612555200Z" />
    <EventRecordID>1</EventRecordID>
    <Correlation />
    <Execution ProcessID="5296" ThreadID="5300" />
    <Channel>Microsoft-Windows-MemoryDiagnostics-Results/Debug</Channel>
    <Computer>TAS</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
      <MemDiagRawData>89170000000000000200000003000000050000000A000000D80300000C0000000200000000000000964017005B090000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C800000000000000707E748DCE00000001000000C800000000000000C8000000000000000C00000038000000DE07080015000C001E00200000000700964017005B09000001000020000001000C00010000000000020001001E00010000000000040001004200010000000000060001002E0001000000000001000100660001000000000003000100EC00010000000000000001000D00020000000000020001001D00020000000000040001004200020000000000060001002F0002000000000001000100650002000000000003000100EC00020000000000</MemDiagRawData>
    </Results>
</UserData>
</Event>
Windows Resource Protection could not start the repair service.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>DISM
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
DISM.exe [dism_options] {Imaging_command} [<Imaging_arguments>]
DISM.exe {/Image:<path_to_offline_image> | /Online} [dism_options]
         {servicing_command} [<servicing_arguments>]
DESCRIPTION:
DISM enumerates, installs, uninstalls, configures, and updates features
and packages in Windows images. The commands that are available depend
on the image being serviced and whether the image is offline or running.
GENERIC IMAGING COMMANDS:
/Get-MountedImageInfo   - Displays information about mounted WIM and VHD images.
/Get-ImageInfo          - Displays information about images in a WIM or VHD file.
/Commit-Image           - Saves changes to a mounted WIM or VHD image.
/Unmount-Image          - Unmounts a mounted WIM or VHD image.
/Mount-Image            - Mounts an image from a WIM or VHD file.
/Remount-Image          - Recovers an orphaned image mount directory.
/Cleanup-Mountpoints    - Deletes resources associated with corrupted mounted images.
WIM COMMANDS:
/Capture-CustomImage    - Captures customizations into a delta WIM file on a WIM Boot system. Captured directories include all subfolders and data.
/Get-WIMBootEntry       - Displays WIMBoot configuration entries for the specified disk volume.
/Update-WIMBootEntry    - Updates WIMBoot configuration entry for the specified disk volume.
/List-Image             - Displays a list of the files and folders in a
                            specified image.
/Delete-Image           - Deletes the specified volume image from a WIM file
                            that has multiple volume images.
/Split-Image            - Splits an existing .wim file into multiple
                            read-only split WIM (SWM) files.
/Export-Image           - Exports a copy of the specified image to another
                            file.
/Append-Image           - Adds another image to a WIM file.
/Capture-Image          - Captures an image of a drive into a new WIM file. Captured directories include all subfolders and data.
/Apply-Image            - Applies an image.
/Get-MountedWimInfo     - Displays information about mounted WIM images.
/Get-WimInfo            - Displays information about images in a WIM file.
/Commit-Wim             - Saves changes to a mounted WIM image.
/Unmount-Wim            - Unmounts a mounted WIM image.
/Mount-Wim              - Mounts an image from a WIM file.
/Remount-Wim            - Recovers an orphaned WIM mount directory.
/Cleanup-Wim            - Deletes resources associated with mounted WIM images that are corrupted.
IMAGE SPECIFICATIONS:
/Online                 - Targets the running operating system.
/Image                  - Specifies the path to the root directory of an offline Windows image.
DISM OPTIONS:
/English                - Displays command line output in English.
/Format                 - Specifies the report output format.
/WinDir                 - Specifies the path to the Windows directory.
/SysDriveDir            - Specifies the path to the system-loader file named BootMgr.
/LogPath                - Specifies the logfile path.
/LogLevel               - Specifies the output level shown in the log (1-4).
/NoRestart              - Suppresses automatic reboots and reboot prompts.
/Quiet                  - Suppresses all output except for error messages.
/ScratchDir             - Specifies the path to a scratch directory.
For more information about these DISM options and their arguments, specify an option immediately before /?.
Examples:
    DISM.exe /Mount-Wim /?
    DISM.exe /ScratchDir /?
    DISM.exe /Image:C:\test\offline /?
    DISM.exe /Online /?
C:\WINDOWS\system32>DISM.exe /English
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Error: 1639
No DISM options were specified on the command-line.
Run DISM with a command-line option specified, such as /Image or /Online. For more information, refer to the help by running DISM.exe /?.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Problems with starting App-v packages in Windows 10

Hello,
I am testing some app-v 5 (sp3) packages on windows 10 (Build 9926). But with some packages I get this Error:
“The application was unable to start correctly (0xc0000142)”. Click OK to close the application"
This package contains Google Chrome 41.
This is the error I can find in the Event Viewer:
Log Name: Application
Source: Application Error
Date: 20/03/2015 13:06:42
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: %computername%
Description:
Faulting application name: chrome.exe, version: 41.0.2272.89, time stamp: 0x54fa819a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x132c
Faulting application start time: 0x01d06306529e9124
Faulting application path: C:\Users\%username%\AppData\Local\Microsoft\AppV\Client\Integration\F6864A3D-8FDB-49D4-9E52-062D22FEA3B5\Root\VFS\ProgramFilesX86\Google\Chrome\Application\chrome.exe
Faulting module path: unknown
Report Id: 917fe03e-cef9-11e4-ab38-00155d016404
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-20T12:06:42.000000000Z" />
<EventRecordID>895</EventRecordID>
<Channel>Application</Channel>
<Computer>%computername%</Computer>
<Security />
</System>
<EventData>
<Data>chrome.exe</Data>
<Data>41.0.2272.89</Data>
<Data>54fa819a</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>00000000</Data>
<Data>132c</Data>
<Data>01d06306529e9124</Data>
<Data>C:\Users\%username%\AppData\Local\Microsoft\AppV\Client\Integration\F6864A3D-8FDB-49D4-9E52-062D22FEA3B5\Root\VFS\ProgramFilesX86\Google\Chrome\Application\chrome.exe</Data>
<Data>unknown</Data>
<Data>917fe03e-cef9-11e4-ab38-00155d016404</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
If I start the same package in Windows 8.1, no problems occur.
Chrome is not the only package that I have problems with.
I am still new in working with app-v.
Has anyone experienced the same problem and found a solution for it?

Hello,
Since Windows 10 is in technical preview I would guess that this is not supported by anyone.
Had one googled this the Three following top-topics would have showed up;
https://support.microsoft.com/en-us/kb/2777003?wa=wsignin1.0
https://packnowledge.wordpress.com/2014/04/28/launching-a-network-executable-inside-an-app-v-5-virtual-environment-revised/
http://blogs.technet.com/b/gladiatormsft/archive/2013/06/11/app-v-5-0-on-these-0xc0000142-errors-and-where-they-are-coming-from.aspx
Nicke Källén | The Knack| Twitter:
@Znackattack

Problems with text using Photoshop CC on Windows 8.1

I am using Photoshop CC on Windows 8.1. I get flickering on the screen as described by others. My main problem, however, is that when I try to use the text tool the layer goes completely black and I cannot see what I am typing or edit the text. I have tried updating my video card driver and my monitor driver. I have deleted the font cache file, I have tried using Photoshop without plug ins (I use Nic plug ins). The only thing that has worked is resetting the preferences by holding down alt+control+shift keys when starting photoshop. This allows me to enter text normally on one photograph and one only. Once I have completed that first photograph and load another I get the black layer. I desperately need help. If this continues I will have to cancel my membership as I was much better off using my Photoshop Elements 11 disc.
Any help will be very gratefully appreciated...............help seems to be very difficult to come by Adobe you make it very difficult for your customers!

Ok,I can appreciate that I may not have given enough information. You state that without proper system information nobody can help, but I need to know what information is needed. You also state that I should simply turn off hardware acceleration in the perfs. What does that mean? How do I do that? I have tried changing the GPU Drawing Mode to basic and it didn't work. Is this what you mean? You may be assuming a level of knowledge I do not have. From research I have done this seems to be a problem with windows 8.1 that Adobe have been aware of for about a year. I have followed all the online advice I have been able to find but nothing seems to be working.
Siren2110

Compatibility problem with USMT 6.3.9600 and Windows Vista

Hi,
We have a problem with USMT 6.3.9600 ()ADK 8.1) while running on Vista. At start we are receiving an error saying it is not a win32 application. USMT 6.2.9200 would work on Vista but not on Windows 8.1.
Any workaround?

For an example with multiple USMT versions, see:
http://blogs.technet.com/b/configmgrteam/archive/2013/09/12/how-to-migrate-user-data-from-win-xp-to-win-8-1-with-system-center-2012-r2-configmgr.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Problem with System Metrics SM_CXSIZEFRAME + SM_CXPADDEDBORDER in Windows 10 Preview (Build 10041)

Similar Messages

Maybe you are looking for