ColorJet 475dw moved not on windows server 2012

During the installation phase, I get a fatal error:

A fatal error occurred prevents use of the product.

Click 'Cancel' to cancel the installation.

No reason. No work around. Reset did not work. Download the basic driver came with the same error.

UPDs are only printer drivers.  There is no reason why you could not take the UPD on a print because of a limitation of scanner server.  UPDs can coexist with separate scan drivers.

If you have to scan drivers and then find http://support.hp.com pilots and the area of download for this printer and your operating system.  Scan drivers are included in the comprehensive software solution.  When a comprehensive software solution is not available while the drivers can be downloaded from Microsoft as a Windows Update.  Once you have the scan drivers so that you can use 3rd party scanning applications to complete your analysis work.

HP has a comprehensive software solution and a basic scan and print driver solution.  Either people should work fine.  If they do not then install the components manually pointing the Hardware Wizard to the installation folder during the analysis of your device manager.

HP keeps a log of installation somewhere under C:\users\\appdata\local\temp.  The directory to search by date and look at all the logs starting with HP.  Review logs and to observe that the last operation was before the error message popped up.  This should help you to isolate what was wrong so you can fix the problem.

Tags: HP Printers

Similar Questions

  • Prerequisites for domain controller promotion is not for windows server 2012

    For windows server 2012 check of preconditions for the promotion of domain controller has failed. TCP ports required by Active Directory Domain Services are already in use on this computer. You must remove or reconfigure the services that currently use these ports (88, 389, 636, 3268, 3269).

    Support is located in the Windows Server Forums:
    http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer/

  • Workstation 8 does not recognize Windows Server 2012 as an operating system

    I want to create a virtual machine using Server 2012 as the operating system, and 8.0.4 workstation does not recognize. My ultimate goal is to create a virtual SharePoint 2013 machine. Is there a workaround? Thanks in advance.

    Do not use 'easy install' then - use rather 'I'll install later' and select 2k8R2 as type of guestOS

  • Windows Server 2012 R2: Error 0x000000C4

    Hello

    I'm having a problem where I can not install Windows Server 2012 R2 (clean install). First: this is NOT a virtual machine. This means that I can not run the command prompt commands of anything like that. in any case, my problem is that whenever I run the Setup, Windows loads the files successfully, but then, just before the Installer starts up, I get a message saying: "your computer must restart. Press and hold the power button. "Error: 0x000000C4". The computer restarts automatically. I never had this problem with Windows Server 2012; It's just with R2 2012. I meet the hardware requirements for WS 2012 R2 so that cannot be the problem.

    Please could someone help me solve this problem. Again, this is not a virtual machine. I know that some people have overcome this problem by running commands for VirtualBox, but I obviously can't do that because I do not have an operating system installed and it isn't VirtualBox.

    Thank you very much.

    This issue is beyond the scope of this site (for consumers) and to be sure, you get the best (and fastest) reply, we have to ask either on Technet (for IT Pro) or MSDN (for developers)
    *
  • Is Adobe Media Server Compatible with Windows Server 2012 5 Professional?

    Could someone from Adobe please check the following link is up-to-date and AMS 5 Pro does not support Windows Server 2012?

    http://www.Adobe.com/products/Adobe-Media-Server-Professional/tech-specs.html

    Thank you

    I'm sure they have one, but I have no idea what it is. It will probably be with a relapse of the AMS service pack in the future. Adobe has not officially supported Windows Server 2012 in one of the applications of the company I have worked with, so don't feel that AMS is excluded.

  • Thumbnail option does not work in Terminal Server in Windows Server 2012 and server session

    This might be a stupid question.

    We have two Windows server 2012 R2 - TS and DC. The clients are connecting to TS and access the shared network drives present in DC. I always unchecked 'show icons, never thumbnails' and 'Show thumbnails in System Properties' enabled on DC and the two TS.

    No always thumbnail option.

    You will need to click on each image. Users have many files containing multiple images. It's annoying to click and view each image.

    Note: NO GPO is configured to block it. Checked.

    I can't find any object GPO to allow this option to be :)

    More info. For customers, anywhere, whether network shares or all folders in TS session. It does not work. Also tried painting and Windows Photo Viewer.

    Here, any help will be very appreciated!

    Hello

    Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

    http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

    See you soon.

  • Windows could not update the Configuration to start the computer. Windows Server 2012

    I am trying to install Windows Server 2012. When installing, I get the message could not Windows Update to the Configuration to start the computer. Installation cannot continue. He cancel the installation. Can someone help me with my problem?

    This issue is beyond the scope of this site and must be placed on Technet or MSDN

    http://social.technet.Microsoft.com/forums/en-us/home

    http://social.msdn.Microsoft.com/forums/en-us/home

  • Cloud management authority seizes not password provided by Cloudstack after the deployment of Windows Server 2012 R2 Datacenter Edition on a virtual machine

    I want to use Windows Server 2012 R2 on a virtual machine. When I start the machine virtual first time, Manager of cloud instance that is installed on the operating system intercepts not created by Cloudstack password. When I reset the password, and then he grabs this new password and I can access VM.

    That's the problem with compatibility with WIndows Server R2 2012 nursery cloud instance? Because the same version of it works well with WIndows Server 2008 R2 VM.

    Hello

    Republish the question to the Forum on TechNet.  These professionals are better able to help you.

    System Center Virtual Machine Manager 2012: improve the private cloud

    http://TechNet.Microsoft.com/en-us/magazine/jj819418.aspx

  • Why not work my product key for Windows Server 2012 RDS CALs?

    I am a member of the partner network and downloaded Windows Server 2012 RDS CALs from my site, I should have 10 licenses (I have not used any to date), but when the installation asks me the key, is not able to verify.

    I'm trying to install on a server of micro Prolient boot from usb because the server is new and has no existing operating system.

    I suggest that repost you this query in the ITPro forums more appropriate.

    But I'm a bit confused - you try to activate the server, or clients?

    they have separate keys

    assuming it's customers...

    http://social.technet.Microsoft.com/forums/en-us/w8itproinstall/threads

  • WinRAR command line tools do not check an executable Windows Server 2012

    Hi all

    I have developed a VI in LabVIEW 8.6 using WinRAR command line tools (passed in the Exec.vi system) to archive data that takes place on 5 different computers on a network and stores on a server .rar files.  Executable file of the VI works perfectly on my computer (WinXP) development.  The data from each of the 5 machines are archived and .rar files are stored on the server.  However, when I move the executable on the server where the .rar files will be stored and run the executable file, the command window flashes on the screen as if WinRAR commands are running, but no data is archived on the server.  No errors are passed out of the Exec.vi of the system.  The server's operating system is Windows Server 2012 and I placed the Rar and UnRAR .exe in the folder system32 on the server.  The server firewall is disabled, and he is able to explore at the location of the data to arhived.  The server is logged in as a domain administrator account.

    Here is an example of one of the commands in command line that I spend in the Exec.vi system:

    cmd /c rar a - m5 \\selsacn11\viscom\selsvis01\15\07\20.rar \\selsvis01\Rep0\Archiv\15\07\20

    When I manually type this command in the command line on the server, the data is stored properly.  The problem occurs when I run the executable on the server.

    I tried to work around the problem by creating a batch of files containing the command above, then using the Exec.vi system to call this batch file.  Yet once, when I manually run the batch file, it works correctly, but when Exec.vi system in a LabVIEW executable file runs the command on the server file, I get the same result as described above - no data are archived on the server.  This batch file works on my development computer and on my laptop to the company.

    My only thought is that there is a problem with the access rights.  So far, the executable works fine on an older server (Windows Server 2003), the development computer (Win XP) and my laptop (Win7) company, but the executable archive not the data on the Server 2012 server or on another computer running WIndows 7.  I have all these machines connected under the same domain administrator account, but COMPUTER networks are certainly above my head, so I wanted to check here if anyone has seen this problem with WinRAR or the Exec.vi system.

    Thanks for any info!

    Success!

    Darin, I took your suggestions and after some more fighting with him, I have an error Code 2 on the Exec.vi system.  This led me in search of the forums where I fell on the following:

    http://forums.NI.com/T5/LabVIEW/problem-using-quot-MSG-quot-command-with-quot-system-exec-VI/m-p/153...

    Of course, all the machines that had been able to run the executable file are 32-bit.  All the machines that could not run the executable are a 64 bit system.  I placed the Rar.exe in the C:\Windows\SysWOW64 folder on the server and it works exactly as expected today.

    I fought with this for weeks, so I'm a little disappointed that it was something so simple, but I'm very happy to have finally work!

    Thank you all very much for the help!

  • PERC H700 driver during Windows Server 2012 r2 - disk Raid not recognized not

    Hello

    I try to install a r2 Windows Server 2012 to a Poweredge R710 with a Raid Perc H700. 2 HDD in Raid 1, but the HARD drive is not rcognized Italian Installation even if I try to use the 2008 r2 for the Perc Raid driver. They are listed, but if I select one disk HARD are not visible. What should do?

    Best regards...

    Grolle,

    Leave in the Raid Controller, what is the status of the table? In addition, was the raid 1 initialized after being created? If this isn't the case, then, who will have to be done before you try to install.

    If you download this and start on the lifecycle controller (F10) and then select deploy BONES, load these files there and proceed with the installation of the OS.

    http://www.Dell.com/support/home/us/en/19/drivers/DriversDetails?driverId=M5VGR&FILEID=3325059394&osCode=MWS80&ProductCode=PowerEdge-R710&LanguageCode=en&CategoryID=DD

    I would like to know how will install it.

  • ML6000 not detected in Windows Server 2012

    Hello

    Our ML6000 is not detected by a new Windows Server 2012 host. It is not found in the Device Manager. However, the 3 SAS LTO 5 inside drives are detected properly.

    It used to be connected only to a Windows 2003 R2 server and is detected without problem. When you are connected to the Server 2003, it originally had 3 SCSI LTO 3 drives.

    For testing and comparison, we place 6 all readers in the library and connected the SCSI 3 Server 2003 R2 and the 3 SAS drives on the server of 2012.

    However, the library is not detected on the 2012. It is detected by the machine of 2003. The two hosts can access the console GUI library.

    The only difference I see between the 2 servers, is that the 2012 server does not have a SCSI card, there is no cable SCSI goes in. But I guess that SCSI connections are just to detect the readers and not the library itself

    What we missed? What type of connection the library should be on the server of 2012 to have detected it in the Device Manager?

    Thanks in advance for your help.

    To use 2 hosts and have 3 drives on each you will have to partition the library and create libraries of logic 2. You put 3 discs each and set a path control for each partition. The path of control allows the host to communicate with the library through its interface scsi or sas.

  • After moving to Windows server 2012 VPN connection error

    Hello world!

    Recently, I upgraded my Windows Server 2003 SB server to a new server running Windows Server 2012.

    I started from scratch by creating a new domain, user, accounts etc.

    The new server is using the same IP address as the old server.

    Since then, I can't connect through the VPN. I have already added the role of remote access on the new server.

    When I try to connect to my Windows 7 laptop, I get this error:

    "Error 800: the remote connection does not because attempts VPN tunnels failed." The VPN server is maybe inaccessible. "If this connection tries to use an L2TP/IPsec tunnel, the security settings required for IPsec negotiation is may not configured properly."

    Any help with this is appreciated.

    Hello

    The question you posted would be better suited in the TechNet Forums. We have a separate team working on the server problem, so I would recommend posting your query in the TechNet Forums.

    TechNet Forum
    http://social.technet.Microsoft.com/forums/Windows/en-us/home?Forum=w7itprovirt

    Hope this information is useful.

  • Fax to Pc ability does not work in Windows Server 2012 for Hp LaserJet MFP Series PCL6 1536

    I have install Hp Solution Center to use the 'Fax to Pc' feature in Windows Server 2012. But it is prevented Windows server 2012. How to use 'Fax to Pc' in Windows Server 2012?

    Sorry, but the Laserjet Printer has no CENTER of HP SOLUTIONS. The Toolbox, it is not the center of need. In addition, it is not compatible with the windows server 2012.

    The printer must be installed on a network in order to FAX to PC.

    1. you will need to type the IP ADDRESS in the address bar on internet. A page with your printer, and you will be set up there.

  • Windows Server 2012 R2 - HF ALL them do not install as "does not apply to this computer.

    Hello

    A general question about patch installs.

    I have several servers which are all Windows 2012 R2.   They don't have internet connections, so I have to install the patches manually.  I have download the HF from the download page of the ISO (https://support.microsoft.com/en-us/kb/913086) every month.    I collect them and install in a facility in bulk during a release cycle (once or twice a year).   I just realized that no. HF have installed since JUNE 2014.  Each HF that appears in the directory WindowsServer2012R2 do not settle with a message "the update is not applicable to your computer.  Which is fine if that was true, but... I get this message for each HF ISO since June 2014.  NOT a single HF, it's applicable to my computer.   Would this be the case?  No HF apply to my 2012 since June of 2014 server systems?

    This is my system information, and below that is the result of any attempt to install 95 HF

    C:\Temp>Systeminfo

    Host name: MYHOST
    Name of the operating system: Microsoft Windows Server R2 Datacenter 2012
    OS version: 6.3.9600 n/a build 9600
    OS manufacturer: Microsoft Corporation
    OS Configuration: Member Server
    OS Build type: multiprocessor Free
    Registered owner: Windows user
    Registered organization:
    Product ID: 00252-80025-36226-AA727
    Original installation date: 13/06/2014, 08:04:39
    Starting system: 16/03/2015, 14:34:45
    System manufacturer: Dell Inc..
    System model: PowerEdge R720
    Type of system: PC x 64
    Processor (s): 2 processors installed.
    [01]: Intel64 family 6 model 62 Stepping GenuineInt 4
    El ~ 2500 Mhz
    [02]: Intel64 family 6 model 62 Stepping GenuineInt 4
    El ~ 2500 Mhz
    BIOS version: Dell Inc. 2.2.2 16/01/2014
    Windows directory: C:\Windows
    System directory: C:\Windows\system32
    Starting device: \Device\HarddiskVolume1
    Local system: en - us; English (United States)
    Input locale: en - us; English (United States)
    Time zone: (UTC-07:00) time of the Rockies (U.S. & Canada)
    Total physical memory: 262 099 MB
    Available physical memory: 249 337 MB
    Virtual memory: Max size: 301 011 MB
    Virtual memory: available: 288 015 MB
    Virtual memory: in use: 12 996 MB
    Office (s) swap file: C:\pagefile.sys
    Domain: mydomain.sgn
    Logon server: \\MYHOST
    Corrections: 25 fixes installed.
    [01]: KB2862152
    [02]: KB2868626
    [03]: KB2876331
    [04]: KB2888505
    [05]: KB2892074
    [06]: KB2893294
    [07]: KB2893984
    [08]: KB2898785
    [09]: KB2898868
    [10]: KB2898871
    [11]: KB2900986
    [12]: KB2901125
    [13]: KB2901128
    [14]: KB2909210
    [15]: KB2909921
    [16]: KB2912390
    [17]: KB2916036
    [18]: KB2919442
    [19]: KB2922229
    [20]: KB2923392
    [21]: KB2925418
    [22]: KB2930275
    [23]: KB2931358
    [24]: KB2931366
    [25]: KB2936068
    Network cards: 6 interconnect installed.
    [01]: Broadcom NetXtreme II 10 GigE (NDIS VB BCM57800
    D Client)
    Login name: ISCSI
    DHCP enabled: no
    IP addresses
    [01]: 192.168.1.30
    [02]: fe80::38c9:e59c:5ac2:e0a1
    [02]: Broadcom NetXtreme II 1 GigE (NDIS VBD BCM57800
    Customer)
    Login name: NIC3
    Status: Hardware not present
    [03]: Broadcom NetXtreme II 1 GigE (NDIS VBD BCM57800
    Customer)
    Login name: MGMT
    DHCP enabled: no
    IP addresses
    [01]: 7.48.64.32
    [02]: 7.48.64.30
    [03]: fe80::f14e:9339:9326:c7fd
    [04]: Broadcom NetXtreme II 10 GigE (NDIS VB BCM57810
    D Client)
    Connection name: SLOT 5 Port 1_swport_VMRepwan
    DHCP enabled: Yes
    DHCP server: n/a
    IP addresses
    [05]: Broadcom NetXtreme II 10 GigE (NDIS VB BCM57800
    D Client)
    Login name: NIC2
    Status: Hardware not present
    [06]: Broadcom NetXtreme II 10 GigE (NDIS VB BCM57810
    D Client)
    Connection name: SLOT 5 Port 2_swport_VMOpswan
    DHCP enabled: Yes
    DHCP server: n/a
    IP addresses
    Requirements for Hyper-V: A hypervisor has been detected. Characteristics required for
    Hyper-V will not appear.

    I have a script that runs each HF installation...   If I manually run them without the tools I get the same results is not the script...

    Install 95 patches
    for Microsoft Windows Server 2012 R2 Datacenter x 64

    The repository path: U:\Patch Repository_4_1\2012_R2_HFs\

    1 Windows8.1 - KB2894852-v2-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    2 Windows8.1 - KB2894856-v2-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    3 Windows8.1 - KB2920189-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    4 Windows8.1 - KB2926765-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    5 Windows8.1 - KB2928120-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    6 Windows8.1 - KB2931358-x 64.msu patch status: ALREADY INSTALLED - JUMP
    7 Windows8.1 - KB2931366-x 64.msu patch status: ALREADY INSTALLED - JUMP
    8 Windows8.1 - KB2933826-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    9 Windows8.1 - KB2939576-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    10 Windows8.1 - KB2953522-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    11 Windows8.1 - KB2957151-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    12 Windows8.1 - KB2957189-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    13 Windows8.1 - KB2957689-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    14 Windows8.1 - KB2961072-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    15 Windows8.1 - KB2961887-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    16 Windows8.1 - KB2962872-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    17 Windows8.1 - KB2964718-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    18 Windows8.1 - KB2964736-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    19 Windows8.1 - KB2965788-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    20 Windows8.1 - KB2966072-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    21 Windows8.1 - KB2966826-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    22 Windows8.1 - KB2966828-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    23 Windows8.1 - KB2971850-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    24 Windows8.1 - KB2972213-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    25 Windows8.1 - KB2972280-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    26 Windows8.1 - KB2973114-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    27 Windows8.1 - KB2973201-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    28 Windows8.1 - KB2973351-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    29 Windows8.1 - KB2974008-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    30 Windows8.1 - KB2976627-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    31 Windows8.1 - KB2976897-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    32 Windows8.1 - KB2977292-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    33 Windows8.1 - KB2977629-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    34 Windows8.1 - X-KB2978668-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    35 Windows8.1 - X-KB2982794-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    36 Windows8.1 - KB2982998-v2-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    37 Windows8.1 - X-KB2987107-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    38 Windows8.1 - X-KB2987114-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    39 Windows8.1 - KB2988948-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    40 Windows8.1 - KB2992611-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    41. Windows8.1 - KB2993651-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    42 Windows8.1 - KB2993958-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    43 Windows8.1 - X-KB3000061-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    44 Windows8.1 - X-KB3000483-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    45 Windows8.1 - KB3000869-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    46 Windows8.1 - KB3001237-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    47 Windows8.1 - KB3002657-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    48 Windows8.1 - KB3002885-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    49 Windows8.1 - X-KB3003057-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    50 Windows8.1 - X-KB3003381-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    51 Windows8.1 - KB3003743-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    52 Windows8.1 - X-KB3004150-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    53 Windows8.1 - KB3004361-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    54 Windows8.1 - KB3004365-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    55 Windows8.1 - KB3005607-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    56 Windows8.1 - X-KB3006226-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    57 Windows8.1 - KB3008923-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    58 Windows8.1 - KB3008925-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    59 Windows8.1 - X-KB3010788-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    60 Windows8.1 - KB3011780-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    61. Windows8.1 - KB3013126-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    62 Windows8.1 - KB3013455-v2-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    63. Windows8.1 - KB3014029-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    64 Windows8.1 - KB3018943-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    65 Windows8.1 - KB3019215-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    66. Windows8.1 - KB3019978-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    67 Windows8.1 - KB3020393-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    68 Windows8.1 - KB3021674-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    69 Windows8.1 - KB3021952-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    70 Windows8.1 - KB3023607-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    71. Windows8.1 - KB3036197-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    72. Windows8.1 - KB3021953-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    73. Windows8.1 - KB3022777-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    74 Windows8.1 - X-KB3023266-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    75 Windows8.1 - KB3023562-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    76. Windows8.1 - KB3024663-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    77 Windows8.1 - KB3029944-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    78. Windows8.1 - KB3030377-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    79. Windows8.1 - KB3031432-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    80 Windows8.1 - KB3032323-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    81 Windows8.1 - KB3032359-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    82 Windows8.1 - KB3040335-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    83. Windows8.1 - KB3033408-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    84 Windows8.1 - KB3033889-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    85 Windows8.1 - KB3034196-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    86. Windows8.1 - KB3034344-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    87. Windows8.1 - KB3035017-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    88 Windows8.1 - KB3035034-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    89 Windows8.1 - KB3035126-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    90 Windows8.1 - X-KB3035131-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    91. Windows8.1 - KB3035132-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    92 Windows8.1 - KB3037634-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    93 Windows8.1 - KB3039066-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER
    94 Windows8.1 - X-KB3044132-64.msu patch status: DO NOT APPLY to THIS COMPUTER
    95 Windows8.1 - KB3046049-x 64.msu patch status: DO NOT APPLY to THIS COMPUTER

    Thank you

    Dave

    Dave,

    It is a forum for specific consumers. You can find the Windows Server support in these forums:

    http://social.technet.Microsoft.com/forums/en/category/WindowsServer>

    Specific Windows Server security sub-forum:

    http://social.technet.Microsoft.com/forums/en-us/winserversecurity/threads>
    `~`

Maybe you are looking for